I'm updating workflow process in Sitecore.
As shown in the screenshot, I added "__OnSave" command under Approval state. I guess it means when user saves the item in Approval state, the state will change to Draft state.
But, it is still in Approval state after saving.
What is the issue??
Actually __OnSave is a command, not an action. I'm not sure if Next State of this command is used at all. You need to click on the command button to execute the command, and __OnSave button is hidden by default.
What you need is another item under your __OnSave item using Auto Submit Action template with properties:
Type: Sitecore.Workflows.Simple.AutoSubmitAction,Sitecore.Kernel
Role: Your chosen role. This action will be executed only for the users which are in the role (e.g. sitecore\sitecore client authoring)
Next state: Workflows/Sample Workflow/Draft
Actions are executed automatically.
Related
Vendor Return authorization is not getting approved through workflow.
Approval status field is set to approved in the final state of my workflow but still the main status of the transaction shows PENDING APPROVAL and the blue colored APPROVE RETURN button appears.
Can anyone advise what is needed to be done to do automatic approval through workflow, below is the screenshot of my Workflow.
On the transition of workflow from "Pending Approval" state to "Approved" state we need to be sure that the transition to approved state happens on a click on a button i.e. Execute on button "Approve". Also, when you click on the transition arrow, you will see (1) condition and (2) "Transition on" options. Having wrong values there can stop the transition. For eg. for "transition on" if you have "After record submit, it will only work on record edit and if it's on entry then it will work when workflow enters new state and if nothing is selected like my screenshot then it will work for all events
Please see image for your reference
Use 'order status' in lieu of 'approval status'.
What status did you use for the rejected field?
In Azure Devops, I can add markdown in a pull request's description to automatically change a linked ticket's state once the pr is completed, like this:
NewState: #TicketNumber
for example:
Committed: #1000
Is there a way to also change the assignee? I have tried:
#PersonName: #TicketNumber
but it didn't apply the change.
You can try using the work item rules to do this.
For example, you can create the rule as when the work item state is changed to completed (Closed, Done, Completed, etc.), set the assignee to the specified user.
To view more details, you can see "Add a rule to a work item type".
However, this method will always assign the work item to the same user who is specified in the rule whenever the work item state is changed to completed.
If you want to dynamically set the assignee according to the user you mentioned in the description, this methods is not available. In this situation, you can try to set up a pipeline with the following steps:
Try to get the linked work item ID, and the account information (username and email address) of the user you want to assign the work item to.
Try using the API "Work Items - Update" to changed the assignee.
I am a new user following this tutorial provided by IBM.
I am up to this step:
For Cloudant Instance, select Input your own credentials and fill in the following fields with the credentials information captured for your cloudant service: Username, Password, Host and Database = guestbook and click Add and then Save.
After following the instruction to 'Add', I am returned to the sequence view (with the list of actions representing the sequence I'm working on).
Expected: The newly created public action w/ binding should appear in the list.
Instead: The newly created public action is not in the list. There is no evidence of it having been created at all. There is no option to 'save'.
Am I doing something wrong? This seems like an enormous bug.
Attempted solutions (unsuccessful):
Log out and back in.
Create new Cloudant service credentials.
Enter service credentials manually vs via dropdown.
Create action in a named package rather than default package.
Create new Cloudant service credentials, selecting a specific service ID.
PS
Attempted to create support ticket but needed to upgrade account by adding credit card. Filled in card information. Card rejected: "Error: Could not place order. Unable to verify the credit card. Declined due to Risk management". I use this card successfully all the time.
In actions UI, selected a sequence, added an action to the sequence, 'reset' sequence to discard changes, began to add yet another action, cancelled that new action, returned to sequence view and the previously created action that I had discarded was there. Ie seems like some backend / database propagation issues on IBM's end?
The steps have been updated in https://cloud.ibm.com/docs/tutorials?topic=solution-tutorials-serverless-api-webapp#sequence-of-actions-to-save-the-guestbook-entry.
To create the new Cloudant binding:
Set Name to binding-for-guestbook.
Set Instance to Input your own credentials.
Set Username, Password, Host and IAM API Key from the values found in the Cloudant credentials for-guestbook created earlier.
Set Database to guestbook.
Set whiskoverwriteLabel to true.
Save
I need to create an alert(preferably configured mail) whenever my SharePoint designer workflow(2013) is suspended due to some error.
Thanks in advance.
Navigate to the Workflow History list in your site (it may be hidden from the Site Contents view, but you can always type in the URL directly <<yourbasesiteurl>>/lists/Workflow%20History/).
Create a view on this list filtered where the Status column is not equal to "In progress", and is not equal to "Completed"
Subscribe to alerts on this View
When a user does not have rights to publish a page, he sees "Request publication" button in Touch UI editor mode. When he clicks on "Request Publication", the workflow "Request for activation" starts and go to the admin's inbox. I want the page to go to some other group for publishing. How can I achieve this?
As shown in the image above, you can change the user/group to be anyone/anything in your instance.
You just need to change properties of default "Request for Activation" workflow.
However, it is recommended to make a new workflow of your own so that upgrades and patches don't revert your changes.
On the /libs/cq/workflow/content/console.html page with all available workflows. You should find workflow that you are interested in.
In you case it is possibly http://localhost:4502/cf#/etc/workflow/models/request_for_activation.html
On this page you can workflow config which contains several steps. Open for editing Request for activation step, switch to tab Arguments and then you can change Name patterns field. It should be regex pattern e.g. .*approver.* for all groups which contains approver in name.
As a variant you can custom workflow or step. In this case you need to figure out by you self how to configure it but usually it is something similar.