Your ArkCase Experience
The specifics of your local ArkCase configuration–the customization and permissions–affect what you see, what options are available to you, and how investigations move through the completion phases. The screens and workflows adapted for your organization may be slightly different than the Core ArkCase examples.
Your organization configures (customizes) the ArkCase installation to the requirements of your business. The Help pages qualify some descriptions with depending on your local configuration when the application could look or behave differently than the core version. Configuration transforms the Core ArkCase framework—use of modules, automated review and approval, access roles and permissions, and the parameters for reporting and audit.
Workflows help ensure that cases and complaints are consistently and correctly handled. Equally important, workflows save time. They automatically perform steps that you don't have to. Workflows are business-based, supporting processes that run in the background.
Pre-defined business actions (events) trigger next steps, for example, the originator submits a request to open a new case, at which time the form automatically routes to reviewers and approvers, and is copied to a folder. The procedure is the same for every new case. The new case form is created and routed in ArkCase. The process does not require separate preparation of a document for review, attaching and mailing the request to a distribution list, or setting a due date for follow up.
Roles and Permissions
ArkCase navigation and viewing is based on role. Your role, and the user group(s) to which you belong, determine the content you can access and the action you can take. Permissions extend to searching. The ArkCase advanced search scans all content that your organization stores. The results will never include content that you do not have permission to access.