Added status remote_realization_broken in Application
We have added remote_realization_broken status in remote opportunity flow. An application can be moved to remote_realization_broken from remote_realized.
Recommended changes on user interfaces
Customer Facing Applications
Recommended changes on user interfaces
Customer Facing Applications
- If you are showing a timeline of an application, you must now represent remote_realization_broken by checking for this status.
- When filtering data for remote realized broken applications, you must also pass "remote_realization_broken" in the filters as well.
Internal Applications
- If you are showcasing statuses of applications or people in a list, you must account for remote_realization_broken status
- If you are showcasing the profile of a particular application, you must check for the status remote_realization_broken
- If you are showcasing a timeline, you must check for the remote_realization_broken status.
- You must add remote_realization_broken status as a filter on all lists for people and applications.
- Added break_remote_realization mutation to mark application as remote realize broken.
- Added permission object can_break_remote_realization in OpportunityApplication permission.
- Added date_remote_realization_broken_at and remote_realization_broken_by in ApplicationMeta .
