Service Descriptions

SKU:	C00001
Description:	AMS team receive, prioritize and resolve incidents in accordance to best practice methods and defined SLA's.
Close description

SKU:	C00002
Description:	AMS team identification and long-term resolution (root cause analysis) of recurring or complex issues within supported applications.
Close description

SKU:	C00003
Description:	Jira Service Management - ticketing system and single point of contact for customer. Accessed through https://novacurasupport.atlassian.net/
Close description

SKU:	C00004
Description:	Includes incident and problem management on delivered solution.
Close description

SKU:	C00005
Description:	Proactive monitoring and maintenance of delivered solution.
Close description

SKU:	C00006
Description:	Proactive patch advice and installations of patches on customer request.
Close description

SKU:	C00007
Description:	Onboarding of customer to Novacura Customer Success.
Close description

SKU:	C00008
Description:	SLA and statistics delivered to customer on a regular basis
Close description

SKU:	C00011
Description:	Single point of contact for Support/AMS when it comes to fulfillment of Support related services including Service Level Agreement, Operations and maintenance activities.
Close description

SKU:	C00012
Description:	Multiple services that can be requested after call-off.
Close description

SKU:	C00013
Description:	Creating a replica or clone of the production database in a separate environment for testing, development or troubleshooting purposes.
Close description

SKU:	C00014
Description:	SLA level Gold offers response times within 2 hours for incidents classified as high priority, 8 hours for medium and 16 hours for incidents classified as low priority. Opening hours for SLA level Gold is 04:30 - 23:00 CEST except for public holidays in customer agreed time zone.
Close description

SKU:	C00015
Description:	SLA level Silver offers response times within 4 hours for incidents classified as high priority, 16 hours for medium and 24 hours for incidents classified as low priority. Opening hours for SLA level Silver is 08:00 - 23:00 CEST weekdays, except for public holidays in customer agreed time zone.
Close description

SKU:	C00016
Description:	SLA level Standard offers response times within 8 hours for incidents classified as high priority, 24 hours for medium and 40 hours for incidents classified as low priority. Opening hours for SLA level Standard is 08:00 - 17:00 CEST, except for public holidays in Sweden.
Close description

SKU:	C00017
Description:	LA level Gold offers response times within 2 hours for incidents classified as high priority, 8 hours for medium and 16 hours for incidents classified as low priority. Opening hours for SLA level Gold is 24/7, 04:30 - 17:00 CEST, weekdays, except for public holidays in customer agreed time zone.
Close description

SKU:	C00018
Description:	SLA level Silver offers response times within 4 hours for incidents classified as high priority, 16 hours for medium and 24 hours for incidents classified as low priority. Opening hours for SLA level Silver is 08:00 - 17:00 CEST, weekdays, except for public holidays in customer agreed time zone.
Close description

SKU:	C00019
Description:	SLA level Standard offers response times within 8 hours for incidents classified as high priority, 24 hours for medium and 40 hours for incidents classified as low priority. Opening hours for SLA level Standard is 9/5 08:00 - 17:00 in customer agreed time zone weekdays, except for public holidays in Sweden.
Close description

SKU:	C00020
Description:	Support on customized objects within an IFS installation, commonly known as CRIM(s) (Configuration, Report, Integration, Modification).
Close description

SKU:	C00021
Description:	Export of data using Oracle tools and utilities, Oracle Data Pump (expdp) or Oracle Export (exp)
Close description

SKU:	C00022
Description:	Extract data from database tables to Microsoft Excel (.xlsx) format
Close description

SKU:	C00023
Description:	Setup Oracle database links to establish connections between different Oracle databases
Close description

SKU:	C00024
Description:	Define, setup and migration jobs based on customer requirements to extract database data and schema structure to another database
Close description

SKU:	C00032
Description:	The complete process of onboarding a customer to Novacura's services post sales. Includes the provisioning of a Customer Success Manager that act as the single point of contact for the customer during its journey as a Novacura customer.
Close description

SKU:	C00025
Description:	Product Support team receive, prioritize and resolve incidents in accordance to best practice methods
Close description

SKU:	C00026
Description:	Product Support team identification and long-term resolution (root cause analysis) of recurring or complex issues within supported applications
Close description

SKU:	C00027
Description:	Jira Service Management - ticketing system and single point of contact for customer. Accessed through https://novacurasupport.atlassian.net/
Close description

SKU:	C00028
Description:	Documentation handover and onboarding of customer to JSM and to support team
Close description

SKU:	C00029
Description:	SLA level Gold offers response times within 2 hours for incidents classified as high priority, 8 hours for medium and 16 hours for incidents classified as low priority. Opening hours for SLA level Gold is 04:30 - 23:00 CET except for public holidays in customer agreed time zone.
Close description

SKU:	C00030
Description:	SLA level Silver offers response times within 4 hours for incidents classified as high priority, 16 hours for medium and 24 hours for incidents classified as low priority. Opening hours for SLA level Silver is 08:00 - 23:00 CET weekdays, except for public holidays in customer agreed time zone
Close description

SKU:	C00031
Description:	SLA level Standard offers response times within 8 hours for incidents classified as high priority, 24 hours for medium and 40 hours for incidents classified as low priority. Opening hours for SLA level Standard is 08:00 - 17:00 CET, except for public holidays in Sweden.
Close description

SKU:	C00009
Description:	Act as Partner Prime towards IFS including submitting bugs to IFS through IFS Service center (requires that the customers agreement with IFS allows this and that the customer is on a supported version of IFS) Follow up on bugs and report status back to the customer Inform the Customer on news from IFS related to both the product and services Request patches and other software related requests on behalf of the customer Act as a trusted advisor to the customer in regards to IFS updates and Oracle updates Escalate cases towards IFS when required
Close description

SKU:	C00010
Description:	Acts as the customers advocate, ensuring customer value of delivered solutions and products throughout the customer lifecycle. Onboards the customer and assists customers getting started with the product or services, can be in close collaboration with the Services Implementation project. The CSM can work in the project but even if not, constantly keeping track of the Customer Onboarding plan. Engages that customer in a proactive way and builds strong relationship with the customer. Knows the customer business and how delivered solution matches the customer objectives. Constantly challenges the customer in terms of gaining increased benefit out of delivered solution and/or potential upsell activities that increases probability to reach customer objectives.
Close description

SKU:	P00037
Description:	The Oracle Connector Service is used to integrate with Oracle with version number 10 and upwards. Oracle changed its version numbering system from version 12, to reflect the year of release instead. After versions 12c, 18c and 19c were released. The letter ‘c’ stands for Oracle Cloud.
Close description

SKU:	P00038
Description:	The SQL Server Connector is used to communicate with Microsoft SQL Server databases.
Close description

SKU:	P00039
Description:	The IFS OData Connector can be used to integrate Flow with IFS Cloud.
Close description

SKU:	P00040
Description:	Address to the IFS Applications Server
Close description

SKU:	P00041
Description:	Address to the IFS Applications Server
Close description

SKU:	P00042
Description:	The Infor M3 API Connector is used to integrate with Infor M3 using the general M3 API.
Close description

SKU:	P00043
Description:	The M3 Rest Connector is used to execute transactions in M3 via the M3-API-REST bulk API.
Close description

SKU:	P00044
Description:	Maximo Generic connector communicates with Maximo Web Services.
Close description

SKU:	P00045
Description:	The SAP BAPI Connector can be used to execute any published BAPI (standard or custom) in an SAP ABAP system, including HANA-based systems.
Close description

SKU:	P00046
Description:	The Oracle Primavera Connector can be used to access Oracle Primavera P6.
Close description

SKU:	P00047
Description:	The Dynamics AX Connector is used to interact with Microsoft Dynamics AX.
Close description

SKU:	P00048
Description:	The Dynamics CRM Connector is used to interact with Microsoft Dynamics CRM.
Close description

SKU:	P00049
Description:	The Microsoft Active Directory connector can be used to perform various Active Directory related operations.
Close description

SKU:	P00050
Description:	The SharePoint 2013 connector can be used to integrate with various apps in SharePoint 2013.
Close description

SKU:	P00051
Description:	Use the email connector to send emails in your workflow. It is possible to use FlowScript in the email connector to make the email more informative.
Close description

SKU:	P00052
Description:	The Web Page Submit Connector can be used to send HTTP POST and GET requests to a given url. At least one parameter must be sent.
Close description

SKU:	P00053
Description:	The FTP Connector is used to upload and download files from an FTP server. It can also perform other operations such as creating remote directories and list files and directories on the FTP server.
Close description

SKU:	P00054
Description:	The SFTP Connector is used to connect to a Secure FTP server (SFTP), including uploading and downloading files. It is also capable of other tasks like creating remote directories and listing files and directories on the SFTP server.
Close description

SKU:	P00119
Description:	The Modbus Connector makes it possible to communicate PLC connected machines and devices using the Modbus communications protocol.
Close description

SKU:	P00120
Description:	The External OAuth 2.0 provider can be used to acquire acess tokens from OAuth 2.0 providers to be consumed in eg the REST connector.
Close description

SKU:	P00121
Description:	The Siox Connector is used to communicate with Siox terminals. Read more on Siox website., and download Siox SDK for the documentations for all the opertations.
Close description

SKU:	P00122
Description:	The REST Service Connector can be used to consume any type of REST services.
Close description

SKU:	P00123
Description:	The Web Service Connector can be used to consume SOAP based web services. It can also be used to consume WCF services that are not based on SOAP, such as net.pipe and net.tcp bindings.
Close description

SKU:	P00124
Description:	The BarTender connector can be used to integrate with BarTender 2016 R8, typically to print BarTender documents.
Close description

SKU:	P00125
Description:	The NiceLabel connector can be used to integrate NiceLabel software, typically to print labels.
Close description

SKU:	P00126
Description:	Use the PDF connector to create PDF files in your workflow.
Close description

SKU:	P00127
Description:	The Flow Environment Connector can be used to read information from the flow 6 database, it can also write new data to said database.
Close description

SKU:	P00128
Description:	The Table Operations Connector is an Internal connector, used to simplify the communication with the Flow Portal, when using Workflow as a datasource.
Close description

SKU:	P00129
Description:	Flow has support for using third party .net assemblies. All public static methods with primitive types as arguments can be executed from a machine step in any type of workflows.
Close description

SKU:	P00130
Description:	The Google API Connector can be used to access Googles public APIs. Currently only URL Shortener API is supported.
Close description

SKU:	P00131
Description:	The Generate Xml Data Connector can be used to write Flow variables to an xml file.
Close description

SKU:	P00132
Description:	The Generate Text Connector can be used to output text either to a file or over the network via HTTP or TCP. Flow variables can be used to compose the text to write.
Close description

SKU:	P00133
Description:	The File System connector can be used to perform directory and file operations on any file system which the Flow Server can access.
Close description

SKU:	P00081
Description:	Flow Classic workflows can be executed within an Android app available for download on Google Play. Supported operating system versions include 5 and up.
Close description

SKU:	P00082
Description:	Scanning can be utilized to input values into controls such as text inputs and list selections, enabling the workflow to automatically progress. However, certain limitations may apply depending on the scanner being used.
Close description

SKU:	P00083
Description:	The client supports offline functionality, enabling users to work without an internet connection. Data is downloaded when online, and can be processed offline. This processing generates transactions, which are stored in a queue. Users can access this queue in Offline data - My Work. Transactions are automatically executed in the background once the device regains internet access.
Close description

SKU:	P00084
Description:	Flow Classic workflows can be executed within an iOS app available for download on the App Store. Supported operating system versions include the two latest major releases.
Close description

SKU:	P00085
Description:	Scanning can be utilized to input values into controls such as text inputs and list selections, enabling the workflow to automatically progress. However, certain limitations may apply depending on the scanner being used.
Close description

SKU:	P00086
Description:	The client supports offline functionality, enabling users to work without an internet connection. Data is downloaded when online, and can be processed offline. This processing generates transactions, which are stored in a queue. Users can access this queue in Offline data - My Work. Transactions are automatically executed in the background once the device regains internet access.
Close description

SKU:	P00087
Description:	Flow Classic workflows can be executed within the Flow Web client. Browsers supported are latest version of Chrome, Edge and Safari.
Close description

SKU:	P00088
Description:	Scanning can be utilized to input values into controls such as text inputs and list selections, enabling the workflow to automatically progress. However, certain limitations may apply depending on the scanner being used.
Close description

SKU:	P00089
Description:	The client supports offline functionality, enabling users to work without an internet connection. Data is downloaded when online, and can be processed offline. This processing generates transactions, which are stored in a queue. Users can access this queue in Offline data - My Work. Transactions are automatically executed in the background once the device regains internet access.
Close description

SKU:	P00090
Description:	A WebForm version is available for the web client, accessible on the Novacura Download site. This version can be utilized if there are limitations in browser capacity.
Close description

SKU:	P00091
Description:	The Portal client is an interactive dashboard client designed for visualization tools. It utilizes workflows as the foundation for actions and data management. Supported browsers are latest version of Chrome and Edge.
Close description

SKU:	P00092
Description:	This is where one defines a list of global variables that are available for usage. By pressing create the user will be forwarded to the definition window to be able to specify a new global variable.
Close description

SKU:	P00094
Description:	Enable presentation mode when the Portal is to be shown, for example, on a big screen in an office or warehouse.
Close description

SKU:	P00095
Description:	With Portal Push Notifications, it is possible to send refresh requests to specific portlets. Portal push notification is located in the Flow Environment connector.
Close description

SKU:	P00097
Description:	The Bar Chart portlet enables users to present data in the form of a bar chart. Users have the option to add multiple series and customize colors according to their preferences.
Close description

SKU:	P00098
Description:	The Column Chart portlet facilitates the presentation of data in a column chart format. Users have the option to add multiple series and customize colors according to their preferences.
Close description

SKU:	P00099
Description:	The Line Chart Portlet enables the presentation of data in a line chart format. Users have the option to add multiple series and customize colors according to their preferences.
Close description

SKU:	P00100
Description:	The Pie Chart portlet facilitates the presentation of data in a pie chart format.
Close description

SKU:	P00101
Description:	The Data Tree Portlet can display a hierarchical structure of data and can be combined with other portlets to, for example, present data belonging to a specific node within that hierarchy.
Close description

SKU:	P00102
Description:	The Document Viewer portlet allows users to view documents directly within the application. It supports displaying documents in PDF format as well as commonly used image formats. In cases where a format is not supported, users will have the option to download the document instead.
Close description

SKU:	P00103
Description:	The Filter portlet enables the creation of customized filter lists and buttons to apply filters to other portlets. Users can select from a preconfigured list of values or manually input a value to send a filter request based on the chosen criteria.
Close description

SKU:	P00104
Description:	The Gantt portlet offers a time-based perspective of your projects and tasks, showcasing the planned schedule for task execution. Within the Gantt chart, users can visualize task dependencies and identify task assignments.
Close description

SKU:	P00105
Description:	The HTML portlet enables the creation of a customized portlet with user-defined content using HTML code. Users can utilize styling and scripts to tailor the content to their preferences and requirements.
Close description

SKU:	P00106
Description:	The HTML Table portlet allows for the customization and presentation of data using HTML code. The HTML table portlet formats the data as a table.
Close description

SKU:	P00107
Description:	The Inbox portlet showcases an inbox containing items, supporting both seed items and handover items.
Close description

SKU:	P00108
Description:	The Kanban portlet provide a visual representation of workflow, enhancing transparency and efficiency in task management, with configurable columns displaying various states, for example.
Close description

SKU:	P00109
Description:	The KPI Cards portlet can be configured to display specific values, such as Key Performance Indicators (KPIs), along with descriptions and units. Users have the flexibility to customize the font size and appearance of the cards, including implementing color rules to enhance visibility and interpretation.
Close description

SKU:	P00110
Description:	The map portlet shows a geographical map into which markers can be placed based on their longitude and latitude values from the marker basic data. A marker can for example represent a work order from the ERP system.
Close description

SKU:	P00111
Description:	The Record Viewer portlet displays one row of a table per page within its interface. Editing can be configured per field.
Close description

SKU:	P00112
Description:	The Scheduler portlet facilitates easy scheduling, display, and editing of appointments or tasks. It offers various time views, including day, week, month, timeline, agenda, or customized views, and supports horizontal and vertical grouping for enhanced organization.
Close description

SKU:	P00113
Description:	The Speedometer provides an overview of a specific value within a defined range. Users can customize the Speedometer to display different colors based on predetermined rules for the value.
Close description

SKU:	P00114
Description:	The Table portlet is utilized for presenting data in a tabular format. Users can configure the portlet to be either read-only or editable. Additionally, data within the table can be formatted by column type, such as text, number, or date. Users also have the option to group data and export it to Excel (.xlsx) format for further analysis.
Close description

SKU:	P00115
Description:	The Text portlet serves to display text, links, and images through a text editor interface. Moreover, it can incorporate information from variables containing data sourced from other portlets by listening to events triggered by these portlets.
Close description

SKU:	P00116
Description:	In the Workflow portlet, users can select workflows and directly assign them to buttons. While a data source can be configured for the portlet to utilize input parameters, it's not necessary for running the workflows.
Close description

SKU:	P00004
Description:	The Novacura Flow Integration Engine simplifies integration management through its web-based administration console. This versatile tool allows users to effortlessly configure environments, define and set up integration services, monitor execution progress, detect issues, and access detailed call history and logs.
Close description

SKU:	P00005
Description:	In Novacura Flow Studio, integration services are first established as Machine Workflows, representing integration routines as business processes. These routines can encompass multiple integration calls to various systems, integrated with additional processing steps such as data mapping. The integration routine editor adheres to a low-code philosophy, ensuring that it's user-friendly and doesn't demand advanced technical expertise for effortless creation.
Close description

SKU:	P00006
Description:	The Integration Engine seamlessly adapts web method input parameters, originally designed for external systems, to match the internal Integration Workflow's required structure. This transformation occurs dynamically, on-the-fly, with each Web-API call. Likewise, the Integration Engine also transforms and aligns the results to ensure smooth and efficient integration processes.
Close description

SKU:	P00007
Description:	With the Integration Engine, a variety of integration services become accessible. These include services initiated by external systems via Web Service (JSON) and services controlled by the Integration Engine Scheduler. When it comes to scheduled integrations, administrators have the flexibility to determine integration call frequencies and configure "Input parameters" for automated workflows. For example, they can set a Region_ID for a workflow that automates sales data integration between different systems.
Close description

SKU:	P00008
Description:	The Integration Engine manages timeout for each integration service call - if the execution completes within the defined timeout, the result is promptly returned (synchronous mode). If the execution exceeds the timeout, the Integration Engine halts it, returning an error code ("http 202 - Accepted but not finished"). The actual result is stored in a dedicated queue for external system retrieval (polling). Timeouts can be tailored for each integration service. Setting it to 0 processes all executions asynchronously, queuing results.
Close description

SKU:	P00009
Description:	The Integration Engine safeguards external systems, like ERP, by regulating the maximum simultaneous executions of specific Integration workflows. It queues integration messages to prevent any loss, and the calling system retrieves integration call results from the queue, similar to timed-out messages. This throttling mechanism can be customized for each Integration flow, ensuring controlled and efficient integration processes.
Close description

SKU:	P00010
Description:	The administrator receives comprehensive notifications for all error-ridden integration calls, accompanied by easy access to in-depth information. Customizable notification rules allow for filtering out errors from test environments, specific error types, or tied to particular integration workflows. Additionally, performance examination is enabled through a dedicated report highlighting workflows that frequently exceed configured timeouts, offering insights for parameter adjustments or optimization.
Close description

SKU:	P00011
Description:	Administrators can conveniently access performance history for individual Integration methods directly from the comprehensive list of all integrations. They have the ability to view the execution history of all integration methods and scrutinize the performance of specific integration calls. Detailed insights include separate displays of each step within the Integration Flow, including step type and name, along with duration compared to the average value for that Integration Flow.
Close description

SKU:	P00077
Description:	Workflow Tasks and Applications can be monitored from the Monitoring section in the Flow Studio.
Close description

SKU:	P00001
Description:	The Novacura Flow Server can be hosted both On Premise or in Cloud (referred to as Novacura Cloud Services). It manages boht all platform related information, like Users, Access, and Applications and exeutes workflows. The Server does not store any data produced by workflow applications.
Close description

SKU:	P00002
Description:	Use the Novacura Flow server management tool to do a new Flow server installation, upgrade and apply service packs.
Close description

SKU:	P00003
Description:	Security Setting controls for Studio availablitiy, time-outs, and account locking. Server security settings are accessed and modified through editing the Web.config file in the Flow Server installation directory.
Close description

SKU:	P00055
Description:	The Novacura Flow Server can be hosted both On-Premise or in the Cloud (referred to as Novacura Cloud Services). It manages all platform-related information, such as users, access, and applications, and executes workflows. The server does not store any data produced by workflow applications.
Close description

SKU:	P00056
Description:	Use the Novacura Flow Server management tool to perform a new Flow server installation, upgrade, and apply service packs.
Close description

SKU:	P00057
Description:	Security settings controls for the Studio availability, timeouts, and account locking. Server security settings are accessed and modified by editing the Web.config file in the Flow Server installation directory.
Close description

SKU:	P00058
Description:	The Flow Studio is a Windows application and the tool used to manage users, connectors, and all other environment information. It is also used to design workflow and to monitor workflow executions.
Close description

SKU:	P00059
Description:	The Studio launcher supports the launching of different Flow studio versions, making it easy to connect to different Flow servers, even when they have different versions.
Close description

SKU:	P00060
Description:	The environment tab is used to adminstrate properties and values which is common for all workflows and creates a context in which the process platform can execute. Users with type AdministerBasicData can access this tab.
Close description

SKU:	P00061
Description:	Designer and Administrator Users can log in to the Studio using either Username/Password or Azure AD.
Close description

SKU:	P00062
Description:	OpenID Connect is an identity layer on top of the OAuth 2.0 protocol. It allows Clients to verify the identity of the end user based on the authentication performed by an Authorization Server, as well as to obtain basic profile information about the end user.
Close description

SKU:	P00063
Description:	A connector is a component that provides Flow with access to remote systems. Depending on the remote system, different authentication methods are used. Connector authentication supports both Global authentication settings (valid for all users) and User Authentication settings, unique for each user.
Close description

SKU:	P00064
Description:	Flow administrators have access to add and remove languages. The added language can be used when designing workflows and can also be selected from the clients to set a preferred language for the entire client interface.
Close description

SKU:	P00065
Description:	Flow Clients support the following system languages: English, Finnish, French, German, Norwegian, Polish, and Swedish.
Close description

SKU:	P00066
Description:	A Full User can log in and run all licensed clients, including the portal.
Close description

SKU:	P00067
Description:	A user type for application packages where an App User can be granted access to a specific Application Package.
Close description

SKU:	P00068
Description:	A Portal User will only have permission to log in to the portal client.
Close description

SKU:	P00069
Description:	A Public User can run a workflow without the need to log in.
Close description

SKU:	P00070
Description:	A Transaction User consumes one transaction for every workflow that is started.
Close description

SKU:	P00071
Description:	A Workflow User will consume one workflow license for every workflow that the Workflow User has access to, granted through the User Roles.
Close description

SKU:	P00072
Description:	Access level that grants access to create applications by graphically drawing workflows.
Close description

SKU:	P00073
Description:	Access level that grants access to all parts of the Flow Studio.
Close description

SKU:	P00074
Description:	Access level that grants access to run Applications. No access to the Flow Studio.
Close description

SKU:	P00075
Description:	In Branding, the logotype and color theme can be customized for the end user. Branding is only available in the Enterprise version of Flow.
Close description

SKU:	P00076
Description:	With the built-in Flow Basic Mobile Security Management all connected mobile devices can be approved, overviewed and managed directly in the Studio or via a workflow.
Close description

SKU:	P00078
Description:	A property can be used from the Flow designer as a constant in a workflow and thereby be used to define different business logic depending from the value of the property. Properties can be defined in two different scopes: Global and User.
Close description

SKU:	P00079
Description:	Under the Reports tab, it is possible to extract reports containing studio data. This can be done, for example, for audit purposes or to check which users are connected to a specific role.
Close description

SKU:	P00080
Description:	It is possible to connect a machine workflow to a specific event that occurs on the Flow server.
Close description

SKU:	P00012
Description:	The Menu is used to construct the content of the landing view for the Flow clients. It can be linked to one or multiple roles, granting access to users with the same role, and a user can have access to multiple menus. The menu can be configured with three types of content: Category, Workflow Item, and Inbox.
Close description

SKU:	P00013
Description:	An Inbox is used in a Menu to notify a user that there is something to do. There are two types of inboxes, Seed inbox and Handover inbox.
Close description

SKU:	P00014
Description:	When working with offline applications in the Flow clients, all transactions that are produced by the workflow are put in a queue. This queue can be found in Offline data - My Work. The transactions are executed automatically in the background when the device has internet access.
Close description

SKU:	P00015
Description:	Machine workflows and User workflows* can be started from a schedule in Novacura Flow. This is useful when a workflow should be run at a certain time or/and with a certain recurrence.
Close description

SKU:	P00016
Description:	It is possible to switch views in Studio from design view to code view. In code view, the code (xml) is presented instead of the graphical representation of it. Code view can help fixing corrupt files which cannot be rendered graphically, allow easy copy of file content and even allow for a quick search and replace.
Close description

SKU:	P00017
Description:	The subscribe function is used to share applications between different Flow environments. This makes the transition of workflows from test to prod very simple.
Close description

SKU:	P00018
Description:	Use swimlanes to involve several users in one flow execution.
Close description

SKU:	P00019
Description:	The Test bench serves as a workflow analysis tool, enabling users to execute workflows and navigate through them while accessing real-time information pertaining to variables, inputs, and tasks. This facilitates the identification and resolution of errors and issues.
Close description

SKU:	P00020
Description:	The version panel will show a list of versions. Any version can be opened by double click. Each version can be in a number of different states.
Close description

SKU:	P00021
Description:	A workflow is a visual representation of a sequence of steps, some of which are to be performed by a user, typically on a mobile device. The workflow consists of user steps, which require the user to do something; machine steps, which connect to underlying systems and databases thru connectors; various flow control steps, which for example tell the workflow how to proceed from the current step to the next.
Close description

SKU:	P00022
Description:	Use the annotation element to add a comment to the workflow. The comment is not visible to end users.
Close description

SKU:	P00023
Description:	Assertion steps are used to perform "sanity checks" on variables in the workflow. An assertion step consists of one or many conditions and an error message to be shown to the operator in case the conditions are satisfied.
Close description

SKU:	P00024
Description:	Use the assignment to create one or many new variables and assign values to them. It is possible to use Flow script to assign a value to the variable.
Close description

SKU:	P00025
Description:	A checkpoint will notify the user with the message that is configured in the checkpoint step.
Close description

SKU:	P00026
Description:	Decision steps are used to take different routes through the workflow depending on the contents of variables or data sources. Decision steps are invisible to the operator. To allow the operator to decide which route to take in a workflow, use a User step in conjunction with a decision step.
Close description

SKU:	P00027
Description:	The end step represents where the workflow is ending. It's possible to have one or multiple end steps in a workflow. Double-click on the end step to edit the output variables or linked workflows.
Close description

SKU:	P00028
Description:	An Event Step can be used to trigger an update to a User Step from either a Timer or from an external device. Available external device types are: Bluetotth LE and Scanner.
Close description

SKU:	P00029
Description:	When working with swimlanes, parallel user inputs can be made. To do this, use the workflow element Split to split the executions into to parallel workflows, this way the original user can continue working in the workflow while the new user works on their swimlane. When the new user is done, use the Join element to join the two parallel executions into one again.
Close description

SKU:	P00030
Description:	The log point can for example be used to measure time or debug workflows. Log points capture the value of the checked variables and can be stored in a database thru a connected workflow in system events.
Close description

SKU:	P00031
Description:	A machine step is used to read or write data from/to other systems, or to modify the variables in a workflow.
Close description

SKU:	P00032
Description:	This item is used to execute a FlowScript program and assign the target variable with the script result.
Close description

SKU:	P00033
Description:	The Split function divides the input string into substrings separated by the delimiter, returning a new table variable with a single value column containing the sub-strings.
Close description

SKU:	P00034
Description:	The start step is created automatically and cannot be deleted. It represents the first step of the workflow and can be configured with start parameters. Double-click on the start step to edit the start parameters.
Close description

SKU:	P00035
Description:	A table is used to make internal tables with stored data just for that specific workflow.
Close description

SKU:	P00036
Description:	A user step contains a sequence of interaction items, like input controls, lists and static texts. Each interaction item type has a number of properties and preferences. Extend User step in the tree beside to read about all the different user controls.
Close description

SKU:	P00117
Description:	The Studio designer is part of the Studio and the tool used to create, graphically design and configure workflows.
Close description

SKU:	P00118
Description:	A fragment is a type of workflow that can be reused multiple times and in multiple user workflows. You connect a workflow fragment to a user workflow using the "Included Workflow" step.
Close description

SKU:	O00005
Description:	99.9% uptime excluding planned maintenance and issues outside of our control
Close description

SKU:	O00006
Description:	All Production environments have the Application Insights service installed. And Non-Production environments can also get Application Insights installed by request. It is used to monitor live applications in Azure. It will automatically detect performance anomalies and includes powerful analytics tools to help you diagnose issues and to understand what users do with our applications. It monitors:• Request rates, response times, and failure rates: Find out which pages are most popular, at what times of day, and where your users are. See which pages perform best. If your response times and failure rates go high when there are more requests, then perhaps you have a resourcing problem.• Dependency rates, response times, and failure rates: Find out whether external services are slowing you down.• Exceptions: Analyze the aggregated statistics or pick specific instances and drill into the stack trace and related requests. Both server and browser exceptions are reported.• Page views and load performance: reported by your users' browsers.• User and session counts.• Performance counters from your Windows or Linux server machines, such as CPU, memory, and network usage.• Host diagnostics from Docker or Azure.• Diagnostic trace logs from applications: so that you can correlate trace events with requests.
Close description

SKU:	O00007
Description:	Here in Novacura, we also configure the Application Insights to check if our applications still accessible from different locations (actually, 3 to 5 different locations) every 5 minutes. The locations are usually selected by region. For example, if an environment is installed in the Central US datacenter, the locations selected to check its availability are usually different datacenters in the US.The Success criteria is HTTP Response 200.The Downtime Confirmation criteria is a timeout of 120 seconds.
Close description

SKU:	O00001
Description:	RPO is age of files that must be recovered from backup storage for normal operations to resume if a computer, system, or network goes down because of a hardware, program or communications failure. Some of the features implemented by Novacura are: - Daily backups of Novacura Flow - 14 Backup retention days for PROD and 7 Backup retention days for TEST - Backups are stored in different datacenters
Close description

SKU:	O00002
Description:	RTO is the quantity of time that an application, system and/or process, can be down for without causing significant damage to the business as well as the time spent restoring the application and its data. Our objective is to restore an environment in 24 hours.
Close description

SKU:	O00003
Description:	Novacura uses automated deployments scripts, which allows that a new instance can be easily recreated in a different location with the same characteristics and configuration existing before.
Close description

SKU:	O00004
Description:	A Staging Slot is used during an application upgrade. Basically, our automated deployment scripts create a new application, with the new software version, and applies all configuration and data existing in the original environment, creating a Staging Slot. Therefore, we do not overwrite the original environment during an upgrade but creates a new one. After its completion, we swap the old environment with the new one, preserving the original application as it was and promoting the new application to production.
Close description

SKU:	O00008
Description:	Front Door will route your client requests to the fastest and most available application backend. Front Door provides a range of traffic-routing methods and backend (e.g., redirecting HTTP request to HTTPS) health monitoring options to suit different application needs and automatic failover scenarios.
Close description

SKU:	O00009
Description:	Natively integrated and platform managed, Azure Web Application Firewall (WAF) provides protection of your web applications from common exploits and vulnerabilities. Web applications are increasingly the targets of malicious attacks such as denial-of-service floods, SQL injection attacks, and cross-site scripting attacks. Preventing such attacks in application code can be challenging and may require rigorous maintenance, patching, and monitoring at multiple layers of the application topology. A centralized web application firewall helps make security management much simpler and gives better assurance to application administrators against threats or intrusions. In addition, a WAF solution can react to a security threat faster by patching a known vulnerability at a central location, instead of securing each individual web application.
Close description

SKU:	O00010
Description:	Each application maintains an Activity Log. It contains all actions performed by users when changing any Azure environment configuration or application status. For example, we can detect when an application was stopped and who was the user taking this action.
Close description

SKU:	O00011
Description:	Our Server Application also has a detailed log information that contains information from external requests received during its execution. These logs are stored locally with the application and retained for 7 days.
Close description

SKU:	O00012
Description:	Our applications can be configured to allow access only to a set of IP Addresses, defined by the Customer. This configuration prevents that our Flow Applications are exposed to requests from any place on the Internet.
Close description

SKU:	O00013
Description:	Another feature that we use to integrate our Flow Applications to other systems is the Hybrid Connection. It allows you to connect the Flow Applications easily and securely to on-premises resources without any changes to your corporate network.Hybrid Connections requires a relay agent to be deployed where it can reach both the desired endpoint as well as to Azure. The relay agent, Hybrid Connection Manager (HCM), calls out to Azure Relay over port 443. From the web app site, the App Service infrastructure also connects to Azure Relay on your application's behalf. Through the joined connections, your app can access the desired endpoint. The connection uses TLS 1.2 for security and shared access signature (SAS) keys for authentication and authorization.
Close description

SKU:	S00001
Description:	TBD
Close description

SKU:	S00002
Description:	TBD
Close description