Skip to end of metadata
Go to start of metadata

The Adeptia Suite user interface is divided into four tabs:

Home

The Home tab displays the home page of Adeptia Suite. Through this tab, you may create new Data Interfaces by selecting the Source and Destination application. It is used to configure activities which can be overridden at execution time of the process flows. Using this interface, you can attach an event with the process flow and the activities that will be overridden at execution time of the process flows.The home page is further divided into four sections: Develop, Execution, Monitor, and Learn. From Develop section, you can develop the solution. From the Execute section, you can execute the solution that you have developed. In the Monitor section, you can monitor the execution of the solution and the Adeptia Suite. Using Learn section, you can access online help, technical documentation and online forum.

Develop

The Develop tab of Adeptia Suite allows developer with process automation role to implement process flows in order to automate them. It includes creation and implementation of all activities and services that are used to create the process flow and then automate it.

Projects

Projects allow you to manage the objects (activities and process flow) as per the projects you are working on. You can create different projects and keep your objects within these projects. You can do all the necessary operation like updation, deletion, etc. from Project page itself. You do not need to navigate to manage pages of these activities.

Data Interface

You may also create new Data Interfaces through the Develop tab.

Process

The Process section of Adeptia Suite allows developer with a process analyst role to document, analyze, and simulate business processes.
This section comprises of the following function:

  • Process Model: to analyze, document, and design effective business process flows. Once the model is created, it also helps simulate the process model.
  • Process Flow: to allow users to create customized process flows using BPMN Notations.

    Services

  • Data Dictionary: to create and define record definitions that are commonly used in schemas. It can be created for following types of schemas:
    • Positional: to create and record definitions commonly used in Positional schemas.
    • EDI: to create and record definitions commonly used in EDI schemas.
  • Source: to identify specific data set (i.e., flat file, XML, or database record) to be created, its location, and the transport protocol to be used to retrieve this data. It can be used to create the following source types:
    • Adv. Database: to specify multiple tables of a database source.
    • Database: to specify a database as a source.
    • File: to specify any file that is located on the local hard disk as a source.
    • FTP: to provide ability to specify any file that is accessible via FTP as a source.
    • HTTP: to specify any file that is accessible via HTTP as a source.
    • JMS: to specify a message of a queue or topic of a JMS Server as a source.
    • LAN File: to specify any file that is accessible on the network as a source.
    • Mail: to specify any file that is accessible via mail as a source.
    • WebDAV: to specify any file that is stored in the WebDAV Server as a source.
  • Schema: This is used to identify how a file is to be read or written. It allows you to define meta-data rules for reading or writing data from text files, database tables, or XML files. It can be used to create the following schema types:
    • Adv. Database: to specify how data from multiple tables can be obtained and inserted in selected tables.
    • Adv. Positional: to read data from a multiple record format positional file and write data into a multiple record format.
    • Adv. Text: to read data from a text file with multiple record format and multiple field separators, and write it into another text file with multiple record formats and multiple field separators.
    • Database: to read data from a database table and to insert/update/delete data into a database table.
    • Excel: to read data from an Excel file and write data into an Excel file.
    • Positional: to read data from a Positional file and to write it into a Positional file.
    • Text: to read data in a pre-defined format from a text file and write it into a pre-defined format in a text file.
    • XML: to read data from an XML file and write it into an XML file.
    • XML Validator: to validate a part or complete XML file.
    • EDI: to manage data in an EDI format.
  • Target: to identify specific data set (i.e., flat file, XML, or database record) to be created, its location, and the transport protocol to be used to send this data. It can be used to create the following target types:
    • Adv. Database: to specify multiple tables of a database as target.
    • Database: to specify a database as a target.
    • File: to specify the name and path of a file to be created as a target.
    • FTP: to specify any file location that is accessible via FTP as a target.
    • HTTP: to specify any file that is accessible via HTTP as a target.
    • JMS: to specify a message of a queue or topic of a JMS Server as a target.
    • LAN File: to specify any file that is accessible on the network as a target.
    • Mail: to specify any file that is accessible via mail as a target.
    • WebDAV: to specify any file that is stored in the WebDAV Server as a target.
  • Web Services: to publish and consume Web Services. It can be used to create the following web services:
    • Security Policy: to create a security policy for a web service.
    • Consumer: to provide ability for a consumer to locate a web service and invoke its operations. It can be located using UDDI and URI.
    • Provider: to publish process flows that are used by a Web Service Consumer.
  • Data Transform: to transform data from one format to another. It can be done by the following methods:
    • Data Mapping: to map and convert source data to target data format. Mapper utilizes the source and target schema activities to enable element-to-element data mapping and application of complex business rules.
    • Record to Record: to take one record at a time and process it according to defined logic using java programming construct and generate output of one record at a time.
  • Extensions: This is used to create custom plugins. It can be done by the following method:
    • Custom Plugin: to create a scripted service that can process data in a customized manner using java-programming constructs and provides an extension point for adding any customized data processing logic.
  • Native Service: This is used to run the .exe, .bat and .sh files asynchronously during the execution of process flow. It can be done by the following method:
    • Native Call: to run the .exe, .bat and .sh files asynchronously during the execution of process flow.
  • Notification: This is used to send e-mail at certain points in a process flow. It can be done by the following method:
    • Mail Notification: to send mail to users about the execution status of a process flow.
  • Polling: This is used to allow the Process flow to 'wait' and 'listen' to the arrival of new or updated data at a pre-defined location before it executes subsequent activities. It can be done by the following methods:
    • Database: to check any changes in the data stored in the database table.
    • File: to check the arrival or modification of file or files on the Local LAN location.
    • FTP: to check the arrival or modification of a file or files on an FTP location.
    • Mail: to 'listen' for the arrival of any mails on the mail Server.
  • Connectors: This is used to define the connectivity to Database Server or JMS Server. It can be done by the following methods:
    • Database Driver: to create a database driver.
    • Database Info: to create database info activity.
    • JMS Provider: to create JMS Provider activity.
  • Miscellaneous: This is used to create the Context Upload and Context Download variables and generate custom reports for process flows that are already executed. It also includes creating of stored procedures. It can be done by the following methods:
    • Context Download: to generate XML from a context variable.
    • Context Upload: to map any field of a schema to the Process Flow Context Variable.
    • Stored Procedure: to encapsulate a set of operations or queries to execute on a database server.
  • Workflow Task: to manage the interaction of a user with the running process flows. You can enter their inputs in the system, in order to automate a decision at a certain point while running a process flow.

Web Forms

  • Web Forms: This is used to create customized forms. They can be created manually, using a pre-defined template or using the Frevvo tool.

Reports and Dashboards

  • Custom Report: to execute a custom report.
  • Dashboard Component: to create components such as Bar Charts, String Charts, Table Charts, and Pie Charts.
  • Dashboard Design: to create the design of the dashboard.

Events

  • The Events section of Adeptia Suite allows developers to define the conditions to execute the process flow. It includes creation of Events and Triggers and binding those events or triggers with the process flow.


This section comprises of the following functions:

Events and Triggers

  • Calendar Event: to specify the recurring execution of process flow between the specified dates in conjunction with a specified calendar.
  • Complex Event: to write your own java logic to trigger a process flow.
  • Database Event: to schedule a process flow to be triggered when a record is inserted, updated or deleted in a database table.
  • Event Registry: to create the event registry.
  • File Event: to specify when and how frequently a process flow should be executed based on either creation of a new file, or existence of a file(s) in a pre-defined location or upon its modification.
  • FTP Event: to specify when and how frequently a process flow should be executed based on either creation of a new file, or existence of a file(s) on a FTP Server or upon its modification.
  • HTTP Trigger: to schedule a process flow to be triggered when an HTTP request is made to Adeptia Suite. It also allows the request to pass the data to the process flow. The trigger can be used by a HTTP client application to integrate with process flow, deployed on the Adeptia Suite.
  • JMS Event: to specify when and how frequently the process flow should be executed if any message is updated in a queue or topic of a JMS Server.
  • Mail Event: to schedule a process flow to be triggered when a specified mail arrives on the mail Server.
  • Timer Event: to specify the date, time and frequency at which a process flow should be executed.
  • Web Service Trigger: to allow a Web Service client to trigger any process flow in Adeptia Suite.

 

Monitor

The Monitor section of Adeptia Suite allows business users along with Process Owners, and Process Participants to perform their daily tasks such as managing their tasks, documents and solutions. It helps Process Owners in monitoring processes, user performance, and viewing their usage reports.
This section comprises of the following functions:

My Tasks

  • Task Manager: to view and manage all tasks assigned to you or your staff (if you are a manager).
  • Task History: to view the history of tasks of a process flow instance or tasks based on search criteria.

My Documents

  • Document Manager: to view and download documents associated with a process flow or tasks associated with a process flow or WebDAV folders using the Document Repository feature.

My Solutions

  • Using My Solutions: These are web-based forms that are created with links by a developer. They appear on the Workspace menu and are used to perform an action such as filling the web-based form, etc.

 

Dashboard

  • Process Flow: to view, execute, and monitor instances of all process flows within a specified date and time range. You can also view details of all tasks associated with a process flow.
  • User Performance: to view and performance of all users. It displays details of all instances of tasks assigned to a user or business role.
  • Data Interface: to view the log of data processing done by Data Interface activity.
  • Events: to view the status of events.

History

The History section of Adeptia Suite allows developer and admin users to view the history of user's actions, events execution, process flow execution, and running of the Adeptia Suite.
This section comprises of the following logs:

  • Audit Trail: to view a list of all changes made to Adeptia Suite activities. It includes creating, editing, deleting, and saving activities. It also includes comments, change of password and login/logout details.
  • Event Log: to view only those messages that are related to triggers and events of Adeptia Suite.
  • System Log: to view all messages associated with Adeptia Suite. It also includes change of password and login/logout details.
  • Process Flow Log: to view details of execution of a process flow and its associated activities. It also includes the status of the process flow (as Parent or Child).
  • B2B Log': to monitor the processing of B2B data such as EDIFACT, X12, HL7, etc.

Reports

This section allows you to view following reports:

  • Usage Report: to view the performance report of a user group.
  • Reports: to view a customized report, which you can define using Jasper Report tool.

Administer

The Administer section of Adeptia Suite allows Sys Admin and Group Admin users with Administrator role to manage users, groups, and business roles. It also allows you to manage Scheduler and Kernel and manage the configuration of the Adeptia Suite.
This section comprises of the following functions:

System Dashboard

  • System Dashboard: to view running Process flows and memory usage of the system. It displays information about the nodes that are part of cluster, details of each node in the cluster and the Process Flow Execution Report.

Setup

  • Application Settings: to view System Configuration and update System Properties of the Adeptia Suite.
  • Group: to create and manage user groups.
  • User: to create and manage users.
  • Business Role: to create and manage business roles.

Maintenance

  • Kernel: to manage the kernel and manage process flow status when the kernel is paused or stopped.
  • Scheduler: to manage the scheduler and manage events when scheduler is stopped.

Security

  • Secret Key: to create, import and export a secret key.
  • Keystore: to create Keystore and import security certificates.

 

  • No labels