Glossary:Flow marker

Flow Marker, flow marker

A rule of type Rule-AutoTest-Case.RunRecursiveTestSuites that supports the testing of flows. If an operator has the AutomatedTesting privilege, that operator can create and use these flow markers.

Flow marker rules belong to a RuleSet and version, but they are not included in the Application Explorer display.

A rule of type Rule-AutoTest-Case.RunRecursiveTestSuites that supports the testing of flows. If an operator has the AutomatedTesting privilege, that operator can create and use these flow markers. Flow marker rules belong to a RuleSet and version, but they are not included in the Application Explorer display.

A rule of type Rule-AutoTest-Case.RunRecursiveTestSuites that supports the testing of flows. If an operator has the AutomatedTesting privilege, that operator can create and use these flow markers. Flow marker rules belong to a RuleSet and version, but they are not included in the Application Explorer display.

Actual work that is performed by application users and automations that consists of a sequence of tasks and leads to an intended business goal. An example of a case is a process of hiring a particular job candidate, where an HR worker collects necessary documents, a hiring manager conducts a job interview, and an application sends an automated email with onboarding information after the candidate is approved. To create a case, you first build a template of your business process that is a case type, and then apply the template in multiple cases, for example, to review applications from many candidates.

An application-specific access control element that is associated with a class and an access role. Using privilege rules in an application is optional, but they can offer improved control over access than access roles alone.

The basic building blocks of an application, rules define the behavior of an application. There are many types of rules, each defining a different type of behavior. For example, rules define the display of a form, the fields that are used in your application, and the flows that define the process of completing work.

The system can reuse rules throughout your application. For example, in an application for ordering replacements parts, you can define a user interface to capture an address, and reuse the same rule for the UI to capture both the mailing address and the billing address for the order.

You define rules in an application to create a business solution for your organization and customers. Rules provide flexibility during the development process and help you design applications more efficiently, so that they can be implemented again in future projects.

A tool that you can use to quickly access records in the current and built-on applications that are available to your operator. These records are organized by work pool, case type, category, and record type.