Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to customize Service Submission Confirmation Page Per Service and based Variables received by BPM #43

Open
8 tasks
StephenOTT opened this issue Jan 28, 2017 · 0 comments

Comments

@StephenOTT
Copy link
Member

StephenOTT commented Jan 28, 2017

The Service submission confirmation page needs the ability to be customized per service and have placeholders that are filled by data that is returned by BPM (such as camunda) post-submission.

Following scenarios/features need to be supported (But lets review first):

  • Per Service Confirmation Messages that are defined by the Service Directory level. Use placeholders ( {{variableName}} ) that are used by variables that are returned by the Camunda Start Instance response.

  • Ability to have Confirmation Message "Templates" that can be centrally defined and then applied to multiple services. This is needed so business staff that are looking to make a bulk change do not have to change dozens or hundreds of services for a small text change. As part of this lets look at if its better to just have Per Service Descriptions that have "block" placeholder rather than the entire confirmation message being a template.

  • Structured variable schema that BPM should respond with. These scheme will be implemented in the BPMN configuration.

  • Ability to customize the "return to dashboard" link? TBD

  • Look at the ability to create "sub-templates" that can be optionally called by BPMN variables. Such as a "Rate your experience" which can defined by the BPMN variable response.


Test the following Key use cases:

  • BPMN returns a Service Level (SLA) and display on confirmation ("Your pothole will be fixed within 5 days")

  • BPMN returns a legacy/Internal system generated case/SR ID number ("Your Case number if 2016-01-5")


Given the potential delay in Syncronous response times from DS -> Camunda -> System X -> and back to Camunda -> DS lets look at the following:

  • Add a "please wait" JS implementation that appears when the user "submits" their Service.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant