ARMATURE Fabric Supplemental Guide for April 2023 Product Release – User Interface, Settings and Configuration Changes

Please use this guide to get a better understanding of some of the UI, settings and configuration changes made within ARMATURE Fabric as part of the April 2023 product release.

User Interface Changes

Cohort Management

Cohort listing includes name, category (new), cohort type, start, and end dates

1. Create Cohort screen
   1. Start and End dates are required fields
   2. A new field “What will this Cohort track?” with two options: Applications, Processes
   3. If Applications option is selected then it will show the list of app types with an ability to select multiple app types
   4. If Processes option is selected then it will show the list of active process definitions
2. Cohort overview screen shows the list of organizations and ability to manage them (add new by clicking + button, remove existing org from the list by checking the checkbox next to the organization and then confirming remove)
3. If Application creation date is in the range of Cohort dates it will show that application next to the organization
4. If Process start date is in the range of Cohort dates, it will show that Process next to the Organization

Setup>Security Users>User Export

1. Additional info (associated person information) is now included in User Export with the ability to filter by ‘Only without Person profile”

Process Management:

1. ARMATURE Fabric now allows you to update the Process Instance display name:

Processes on Application

1. An activities tab is now the default tab on Application overview
2. It will show all processes for this application with detailed view (tiles) for each activity that is In Progress.
3. Staff will have two tabs under each process - My Activities and Milestones (only if Milestones are set up in the process definition). Org Rep will have three tabs – My activities, Milestones, Completed (will show activities that were completed and Org Rep has access to).

Organization Representative Views:

Staff view:

Auto-Start Application Process

There is a new setting on Application Type (Setup>Certifications>App type>APPLICATION CREATION PROCESS DATA KEY(S)) that allows an auto-start application process on Create. When a user adds a process definition data key (multiple data keys can be added) to App Type then it will auto- start that process on creation of this type.

We have also added the ability for you to NOT allow a user to create a new application (per organization) of the same type when any are open (Not abandoned, Not completed). This can be configured in Setup>Certifications>App type.

Extensions (User Interface update)

Also affects old forms (entities).

Applications

Stopped showing "active process stage name" as a status on the main Application view (it is still available in the Application listing).

New setting on Instrument Scheduling stage in the process definition

When Stage moves to In Progress then automation will be triggered:

1. A new function to auto-complete Instrument scheduling stage when all Instruments are scheduled (auto-completion will be triggered only if there are required instruments on the stage and all of them are completed. If there is an optional Instrument, then stage won’t be auto completed). See screenshot above for new setting.
2. Auto complete Instrument Response stage or Instrument Form submission stage when all responses/forms are submitted. Cannot auto complete if any “allow multiple” instrument forms or optional responses/forms.
3. UI for navigation from Instrument Response back to application was improved.

Settings and Configuration Changes

Processes

1. A new function to auto-schedule Instruments:
   1. applies to stages that are type “Instrument Scheduling”
   2. this setting should not apply to “Instrument Form Submission”
   3. will auto schedule an instrument that is marked required on the stage
   4. will not schedule any optional instruments
   5. will schedule against the latest non-archived published instrument
   6. set the open date of the response to current date
   7. set the close date of the response to empty
   8. set the context entity (likely application) to the same as what is on the process
   9. set private = false
   10. set require completion = value on published instrument
   11. no support for static variables
   12. no support for direct assignees 

New setting on Instrument Scheduling stage in the process definition:

When Stage moves to In Progress an automation will be triggered.

1. A new function to auto-complete Instrument Scheduling stage when all Instruments are scheduled (auto-completion will be triggered only if there are required Instruments on the stage and all of them are completed. If there is an optional Instrument, then stage won’t be auto-completed). See screenshot above for new setting.
2. Auto complete Instrument Response stage or Instrument Form submission stage when all responses/forms are submitted. Cannot auto complete if any “allow multiple” instrument forms or optional responses/forms.
3. UI for navigation from Instrument Response back to application was improved.

Changes to Instrument Response Tabs

Issues tab

1. Issues tab should be shown from within a review cycle if the review cycle is configured to allow issues
2. If a review cycle is configured to allow issues:

• Review Presenter will display Issues tab (similar to Documents tab)
• Review Presenter will allow a reviewer to manage issues against parts that are configured to allow issues

1. Issues tab should NOT be shown from within a review cycle if review cycle is not configured to allow issues, but allowed on a response
2. The following issue has been fixed: Issue tab is missing when accessing Instrument response without Issues allowed and then accessing Response with Issues allowed

Documents tab

1. A new permission on Instrument Responses for replacing documents on completed response/review
2. Documents tab was hidden in Offline Mode

New Setting in Customer Settings for Org Rep to Manage Documents

1. Create documents
2. Download (If this setting is enabled, documents tab will be shown. Note: If user can create, but not read, documents tab will NOT be shown)
3. Edit (Editing the name of the document)
4. Replace
5. Delete

Note that the Org Rep can only view and download Shared docs.

New Permission to Manage Shared documents

1. Mark non-shared document to share → controlled by Share permission
2. Remove a document from being shared → controlled by Share permission 
3. Add more PPO to an existing shared document → controlled by Share permission

New Permission to Update Documents that are Shared

• Replace, edit, remove

Directory Functionality Change

• Country code now added as a listing option

Froala Editor Update

1. Includes multiple fixes in different areas of the system
2. Added a single toolbar at top of the Instrument Builder/Instrument Response/Review Page, instead of a toolbar for each rich/narrative field

Events

1. Business id was added for entities under Review items tab on Event
2. Fixes related to Org rep not being able to access Focused event
3. Org rep users should not be able to unlink and create focused event from the process stage (My items user will still have such options)

Instruments

• Added support for “year” data input under the number question type. It requires a 4-digit numeric input and will not display any comma designator when value is entered in the Instrument response/review.