<Proposed capability name. Should describe the capability in max 4 words. e.g. Creating Merit Certificates>
<Summarize the capability by answering the questions ‘Why are you developing the said capability?’ i.e. what problem is the capability trying to resolve, and ‘What is your proposed solution?’>
<Sample text:
States and organizations feel the need to motivate and recognize deserving learners.
To address this need, States/organizations can issue Merit certificates from DIKSHA. However, since the criteria for merit cannot be standard, we propose to make the merit criteria (rules) configurable. The parameters that States/organizations can set are:
...
who will get the certificate (all users or select few),
...
when (on completion of assessment or based on a score, or both)
...
Browser flow for first time users
Improving the the browser flow experience for first time users of who would want to use the Admin capabilities or assets on Diksha website.
Today when users come on the DIKSHA website they are asked to fill in their Board, Medium and Class and then select their relevant role on the platform both as guest users and as logged in users
The Board , Medium and Class are mandatory information that needs to be filled by the users before they proceed.
When a primary role of the user is HT&other official on the platform the Board, Medium and class information is not important and hence we want to make this information optional on the website. So users can fill or skip the information which is not relevant.
Direct Access to Form
Simplifying user experience on the App when the users want to access observation form.
Today when users access the form on the App, they have to preview it and and come back to the listing page and then start the form.
With the new design , now users can click the form and directly preview it and start the form from the preview page itself without having to do the additional step coming back to the listing page and start the form.
Mandatory task and subtask for a project
This enhancement is for the improvement project capability on the App. A designer of the Improvement project can mark certain tasks and subtasks as mandatory. By doing so the designer is asking the users to take those tasks and subtask as it is (without making any edits to the recommendation by the creator)
The tasks and subtasks which are mandatory, users will see a tag under them that these tasks and subtasks are mandatory
The mandatory tasks and subtasks cannot be edited or deleted by the user.
A subtask can only be mandatory when the Task (parent of the subtask) is mandatory
Additionally a Mandatory task which has a observation type asset attached to it can only be marked as in progress.
The above mentioned behaviors and conditions will be enabled in the front end when a creator has marked a task and a subtask under a task mandatory.
Sequencing of tasks in a project
This is an enhancement to the existing project templates, to ensure users see a logical sequence to the tasks to the projects targeted to them.
Today when a project is targeted to the users they see a list of task which are not sequenced in any order in the project template.
The sequencing happens based on the end date given to the task by the user.
This capability will ensure that users can see the logical order of the tasks provided by the creator.