React Task Configurations - kwantu/platformconfiguration GitHub Wiki
All the task configurations
In task there are two out of three types of tasks are implemented
- open - Opens the existing process created by some server actions on workflow movement of any step
- instantiate - prepares a UI with a button that can instantiate a new sequence or new instance workflow. If it is new instance instantiate like in case of "Record Engagement Meeting" it presents with a button to create a new workflow and another link to open the created instances in a list view. If it is instantiate with "type": "newSequence" means it will create the workflow if not created else will open for editing if not complete else create new sequence if current sequence is complete.
Monitoring a step -
- A workflow is either monitored or unmonitored. Unmonitored means will act normal as per the workflow rules. If one step is captured workflow will move to next step if default transition is true and will assign to user as workflow rules say. It follows workflow Statuses.
- If it is a monitored workflow means that task is responsible to capture that sepcic step only and will be back to task page. Monitored workflow has its own special statuses "Underway" and "Complete" . If monitored step is passed it marks that task as Complete else Underway.
BEEI - Task Type Technical Documentation
Overview
This document provides a technical breakdown of different taskList.taskType
configurations found across multiple stages. Each task type is categorized based on its process, monitoring configurations, and UI interactions.
1. Update School and Timekeeper Details
stage1
Stage: Task ID: updateSchool
taskType: open
Process: RegisterSchool
Configuration:
{
"open": {
"process": "RegisterSchool",
"button": { "i18n": { "en": "Update school" } }
}
}
2. Candidate Selection
stage1
Stage: Task ID: candidateSelection
taskType: open
Process: SchoolCandidateSelection
Configuration:
{
"open": {
"process": "SchoolCandidateSelection",
"button": { "i18n": { "en": "Select candidates" } }
}
}
3. Update Assistants' Details
stage2
Stage: Task ID: updateParticipantDetails
taskType: open
Process: updateProfile
Configuration:
{
"open": {
"process": "updateProfile",
"button": { "i18n": { "en": "Update assistants" } }
}
}
4. Update Bank Details
stage2
Stage: Task ID: updateBankDetails
taskType: open
Process: ParticipantBankDetails
Configuration:
{
"open": {
"process": "ParticipantBankDetails",
"button": { "i18n": { "en": "Update bank details" } }
}
}
5. Prepare School Payment File
stage3
Stage: Task ID: updateAttendanceAndPayments
taskType: open
Process: SchoolPayfilePrep
Configuration:
{
"open": {
"process": "SchoolPayfilePrep",
"button": { "i18n": { "en": "Prepare file" } }
}
}
td-5b8aa9fd-709c-4d20-b48a-c65c3135d932-1-stage1.json
td-5b8aa9fd-709c-4d20-b48a-c65c3135d932-1-stage2.json
td-5b8aa9fd-709c-4d20-b48a-c65c3135d932-1-stage3.json
CSC - Task Type Technical Documentation
Overview
This document provides a technical breakdown of different taskList.taskType
configurations found across multiple stages. Each task type is categorized based on its process, monitoring configurations, and UI interactions.
1. Record Engagement Meeting
stage1
Stage: Task ID: recordEngagementTask
taskType: instantiate
Process: meeting
Configuration:
{
"instantiate": {
"monitor": {
"monitorStep": "captureForm",
"monitorSet": "SDOengagementMeeting",
"monitorView": "object"
},
"process": "meeting",
"labelText": "#COUNT meetings added",
"button": { "i18n": { "en": "Record meeting" } },
"modal": {
"label": { "i18n": { "en": "Meeting name" } },
"inline": { "i18n": { "en": "Enter name " } }
}
}
}
2. Register a Focus Group
stage2
Stage: Task ID: focusGroupIdentification
taskType: instantiate
Process: GroupScorecards
Configuration:
{
"instantiate": {
"process": "GroupScorecards",
"labelText": "#COUNT groups added",
"monitor": {
"monitorStep": "captureForm",
"monitorSet": "CAREgroup",
"monitorView": "object"
},
"button": { "i18n": { "en": "Register group" } },
"modal": {
"label": { "i18n": { "en": "Group name" } },
"inline": { "i18n": { "en": "Enter name " } }
}
}
}
3. Record Group Issues
stage3
Stage: Task ID: recordIssueGeneration
taskType: open
Process: GroupScorecards
Configuration:
{
"open": {
"process": "GroupScorecards",
"monitor": {
"monitorStep": "recordIssues",
"monitorSet": "CAREscorecardissuedevelopment",
"monitorView": "object"
},
"button": { "i18n": { "en": "Enter issues" } }
}
}
4. Review Consolidated Issues
stage4
Stage: Task ID: reviewConsolidatedIssues
taskType: instantiate
Process: consolidatedScorecards
Configuration:
{
"instantiate": {
"type": "newSequence",
"process": "consolidatedScorecards",
"labelText": "Consolidated Issues",
"button": { "i18n": { "en": "Prepare consolidated issues" } },
"editButton": { "i18n": { "en": "Review consolidated issues" } }
}
}
5. Indicator Development
stage4
Stage: Task ID: recordIndicatorDevelopment
taskType: instantiate
Process: Indicator
Configuration:
{
"instantiate": {
"type": "newSequence",
"process": "Indicator",
"monitor": {
"monitorStep": "captureForm",
"monitorSet": "CAREscorecardindicatordevelopment",
"monitorView": "object"
},
"labelText": "Indicator added",
"noWorkflowView": true,
"button": { "i18n": { "en": "Create indicators for scoring" } },
"editButton": { "i18n": { "en": "Edit indicators for scoring" } }
}
}
td-fbe165a3-18ad-48a0-8216-90682abb0ae2-3-stage1.json
td-fbe165a3-18ad-48a0-8216-90682abb0ae2-3-stage2.json
td-fbe165a3-18ad-48a0-8216-90682abb0ae2-3-stage3.json
td-fbe165a3-18ad-48a0-8216-90682abb0ae2-3-stage4.json
td-fbe165a3-18ad-48a0-8216-90682abb0ae2-3-stage5.json
td-fbe165a3-18ad-48a0-8216-90682abb0ae2-3-stage6.json
td-fbe165a3-18ad-48a0-8216-90682abb0ae2-3-stage7.json
td-fbe165a3-18ad-48a0-8216-90682abb0ae2-3-stage8.json
td-fbe165a3-18ad-48a0-8216-90682abb0ae2-3-stage9.json
Usage
This documentation can be used for reference when implementing new task types or modifying existing workflows in the project.