faq-bgs
assistedge-discover-thumb

Can we visualize the various raw fields across multiple applications on a single report/screen for each user?

The data collected from users are anonymized. Therefore, the product doesn’t allow segregation of data for a named user. Individual recording can be viewed to the process management screen.

The user starts and stops the Discover client utility to record the process execution with the preconfigured process ID. The tagging of individual records is used during process mining to generate the process map based on these recorded empirical data. The tool also supports capturing data without doing start or stop of Discover Client utility as per the configuration done on Discover Admin module. In this case, the tool will capture all the activities performed by user.

The user starts and stops the Discover client utility to record the process execution with the preconfigured process ID. The tagging of individual records is used during process mining to generate the process map based on these recorded empirical data. The tool also supports capturing data without doing start or stop of Discover Client utility as per the configuration done on Discover Admin module. In this case, the tool will capture all the activities performed by user.

The user starts and stops the Discover client utility to record the process execution with the preconfigured process ID. The tagging of individual records is used during process mining to generate the process map based on these recorded empirical data. The tool also supports capturing data without doing start or stop of Discover Client utility as per the configuration done on Discover Admin module. In this case, the tool will capture all the activities performed by user.

For a single recording, each block is an application toggle, and within each block the user can see multiple events/actions. For the final workflow (consolidated recordings) each block is an event / action carried out by users.

Practically every exception is a variation in the workflow. The tool provides capability to the user to remove individual transaction from being part of process analysis, which seem to be an exception.
Whether a transaction is a noise or not, it depends on the quality of data, and how the neural network algorithm statistically handles it.

Practically every exception is a variation in the workflow. The tool provides capability to the user to remove individual transaction from being part of process analysis, which seem to be an exception.
Whether a transaction is a noise or not, it depends on the quality of data, and how the neural network algorithm statistically handles it.

The process SME would be needed to analyze the process map, and validate the requirements identified by the business consultant. Also, the prerequisite software should be installed before deploying Discover.

The workflow can be downloaded into a document and can be edited outside of the product.

Multiple LoB / Workgroups of the same organization can be configured on the same admin portal. All the configurations related to that workflow can be managed by the respective administrators. Data access and visibility is restricted to the workgroup level.

The neural network algorithm that is used is LSTM (Long Short Term Memory). Machine learning is used to identify the pattern of the process flow from the raw recordings.

Windows events and emulator related details are getting captured, but might not get the details of applications accessed via Citrix.

Yes. Each session, the Discover Client utility will start data capture exe. For each session, different instances of Discover will run.

The tool doesn’t eliminate any user action, and hence noise removal based on application is not possible.

Based on App / Control type, the product doesn’t capture data as soon as it identifies a particular field as password type. No additional configuration is needed.

At present, the user who is capturing the data needs to start and stop the process monitoring during execution of each transaction of the process.

The Discover Client can monitor activities on SAP with the limitations mentioned in the product boundary document. Window events for Siebel activities are captures, but field level data are not captured at present.

At present, the product supports Rumba emulator for Mainframes. Data capture from other emulators and Linux machines are not possible at present.

Yes, the captured data on client machine is encrypted with Windows Data Protection API. In transit, it is protected with HTTPS, and TSLv1.2+.

Yes. The product allows using business policies framework.

The product currently shows blank Start or Stop time in case respective markers are not available, which will help users to exclude those cases from Process Analysis.

Individual recording can be identified as a noise and removed from the process management screen before the mining is executed. During the mining, the algorithm takes a call on noise purely on the basis of statistical parameters.

Screen capture may potentially expose the personally identifiable information. Hence, it is not supported by the product at present.

The “delete” option provides user the capability to exclude a specific recording from Process Analysis. Editing of workflow may potentially hamper the empirical variations in process execution, hence the tool doesn’t support it.

Yes. It can be achieved by doing new recordings of process execution, and then generating the process map after selecting the appropriate data range.