We had a recent design session by making use of Blueprint to re-imagine an existing case. However, when it comes to the Preview App feature, business stakeholders have high expectations to review the views, layouts of the E2E journey in the preview itself. I understand, Preview App does not create real time cases behind the scene - it is good to set the expectations clear as to what is the purpose of the feature and its capabilities. Has anyone faced similar situations, if so how did you address it? Please share insights if any.
@SPKarthikThanks for sharing your thoughts here. Could you please share more details around the gaps which were observed by the stakeholders during your design session.
Business Stakeholders expects to have user experience testing in preview app feature of Blueprint
This includes how & where fields in the views are displayed. As we know “How” is driven by Data model which can be tacked but not the “How”
Whether the fields in the views (as part of a step) makes sense from user experience perspective
At times, the initial modal dialog when clicking on a new case in the preview, is not popping up.
Business Stakeholders expects to an image with processes to be converted to a Stage rather than a case type
Expectation on the support of images to be uploaded to be conceived as a case type within the work flow details for every case type instead of just bpm file.
@SumanKumar I would like to correct typos in the below statement
Business Stakeholders expects to have user experience testing in preview app feature of Blueprint
This includes how & where fields in the views are displayed. As we know “How” is driven by Data model which can be tackled but not the “Where”
Whether the fields in the views (as part of a step) makes sense from user experience perspective
At times, the initial modal dialog when clicking on a new case in the preview, is not popping up.
Business Stakeholders expects to have an image with processes uploaded, which is then converted to a Stage rather than a case type
Expectation on the support of images to be uploaded to be conceived as a case type within the work flow details for every case type instead of just bpm file.
Business Stakeholders expects to have user experience testing in preview app feature of Blueprint
This includes how & where fields in the views are displayed. As we know “How” is driven by Data model which can be tackled but not the “Where”
Whether the fields in the views (as part of a step) makes sense from user experience perspective
At times, the initial modal dialog when clicking on a new case in the preview, is not popping up.
Re 1.1 The involvement of Constellation plays critical and important part, where the “what” gets displayed is driven by underlaying data model and “how” and “where” is handled by Constellation, be it a preview in the Blueprint or your actual Application authored subsequently via App studio. This is done to primarily achieve two things 1. The consistency in the UI and overall user experience 2. Configuration speed - where the “how” and “where” is determined by underlying rendering engine once “what” to display in authored for given view.
Re 1.2 - whether the fields rendered makes sense from UeX perspective - this will depend on your underlying business process and can be verified by leveraging Blueprint preview feature.
Re: 1.3 - this may be a bug and may need further investigation but also depends on what is the first step in your workflow
2. Business Stakeholders expects to have an image with processes uploaded, which is then converted to a Stage rather than a case type
Not strictly related to preview functionality, but understood what you are trying to achieve, at present a BPMN file can be added to build a lifecycle but not an image. this may get enhanced in the future.
3. Expectation on the support of images to be uploaded to be conceived as a case type within the work flow details for every case type instead of just bpm file.
Again Not strictly related to preview functionality as above