I am having a requirement where if am selecting a step response for a workitem in workflow map , i need to restrict it to a data field for taking that action.
For example if am having a step name as'XYZ' and i am selecting the step response' ABC' it should restrict the workitem to be routed to the next step in the workflow by any pop-up window or any alert window in IBM workplace application. I should be able to route the workitem to next step by selecting the step response 'ABC" when the step name is not 'XYZ'
Is this possible in workplace application to achieve this.
I know in IBM Case manager we can restrict the workitem from routing it to the next step with the script adapters in page level. Similarly is there way to achieve this in Workplace application also at the workflow level or something. Please advice.
I have tried adding a condition along with the step response to achieve this. But the workitem is getting terminated if doesn't match the condition.
For example. I have addition the condition as ' All(ABC) and Stepname<>'XYZ' in the conditional route in workflow map. But if i override the condition the workitem is getting terminated.
Related
Using an example scenario where a user needs to shop for flights, via these Steps:
Select Outbound Flight, go to next page
Select Return Flight, go to next page
Enter Billing Info, go to next page
On The confirmation page - submit info
Now I know that Cypress is all about building up state programmatically rather than going through the steps via the UI. So for the smoke test would I want to only start the test from Step 4, feed it a previously set state and make sure there is no error upon submit?
Also what about the other pages - would it be ok to have one end to end test that goes through Steps 1-4 purely via the UI?
There are 2 ways of potentially achieving this.
1. Using Rest API in cy.route, More info here: https://docs.cypress.io/api/commands/route.html#Usage
2. If the site appends query parameters to the url e.g. www.flightsight.com/?from=london&to=chicago, you can give this URL in step 4.
If the site uses POST request, then these parameters unfortunately won't be available.
I am new to Microsoft Unified Service Desk, therefore please pardon me if i make any mistake.
My scenario is when a call is received by a call center agent in Unified Service Desk then initially he will create a case for the particular customer and initially the caseID will be null therefore call center agent will see a new case window where he can create a case. Once the case is created he will save the details and the caseID will also be saved. Now, in the next step he will transfer the call to the supervisor and in this case the supervisor will not see a new case window instead he will have the details in-front of him of that particular customer that were saved earlier.
But how will i achieve that do i have to create a hosted control and is there a way i can execute JavaScript inside hosted control.
Looking forward to your help.
Thanks.
What you need to do is.
Create 2 Action Calls.
1st Action Call for New Case with Action New CRM Page.
2nd Action Call for Open Case with Action Open CRM Page.
Put Condition inside Action 1 [[$Settings.YourCaseID]]==""
Put Condition inside Action 2 [[$Settings.YourCaseID]]!=""
Create another Action with SaveSetting Action and CRM Global Manager hosted control.
Once the case is saved fire the third action call (It will save the CaseID inside $Setting).
Now when the case is transferred it will open the case with SavedID.
I have a scenario where the user wants a check in place to ensure that all tasks have been completed before moving onto next stage on the Business Process Flow.
Is there anyway to do this?
2 ways to achieve it.
Option 1: Create a bool field - Tasks closed? & keep that in BPF step, if it’s true then platform will also users to move forward. Otherwise not.
You can mark this as read-only, write a plugin on Task completion to update this as yes, when there is no more open tasks.
Read more
Option 2: Can have a js validation onStageChange or onSave to retrieve open child tasks, check the count, show notification & preventDefault.
Read more
You can do the same in pre-update plugin, throw InvalidPluginExecutionException if there are open tasks.
In the scaffolded module there are two alternatives of the actions defined: a window action and a server action.
But what is the difference of those actions conceptually and when to use which of them?
In Window action, we are register Tree,Form,Kanban,Calendar etc ids. Based on priority, it will open related view.
While Server action are useful for following different-different purpose with selected Base model.
Send Email
Execute Python Code
Trigger a Workflow signal
Run client action
Create or Copy a new Record
Write a Record
Execute several actions
I was wondering if anybody ran into the same issue as I am facing now.
What I'm trying to do is have a workflow that checks the condition of a field (optionset) of a form. If the field has option 1, 2 or 3 then create new record with certain shared attributes, otherwise start a child workflow. The child workflow is a "Dialog" process, not a "workflow" process which informs the user that the record was not created and why. For some reason I cannot select the dialog workflow from the dropdown list of available child workflows...
Both the parent workflow and the "dialog" workflow process are based on the same entity.
If anybody has any ideas on how I could debug this or any clues in general I would greatly appreciate your feedback.
Thanks for taking the time to read this post!
It is not possible to call a dialog from a workflow (see here).
Workflows are generally triggered by events.
Imagine the ramifications - which user would receive the dialog and what if no-one was logged in?
One option is to drive everything with JavaScript
Trigger on change of the option set
Create the records
Start the workflow
Start the dialog
See the section under the heading "Opening a Dialog Process by Using a URL" on MSDN here
Rather use the URL than showModalDialog or showModelessDialog.
What might work even better is to call an Action from JavaScript. The Action can run synchronously and create all records, start child workflows and dialogs.
A synchronous workflow can stop an event and return an error message to the user, but cannot return success messages - it look like this will not meet your requirements, but Gareth Tucker has an example here.