Workflow Launcher

Workflow Launcher

You should not call your processes as part of the DAM Update Asset Workflow instead. This blog will take you on an introductory tour of how to create a simple workflow, a launcher and custom steps. Content Managment " Workflow Starter Drawing on my earlier article on Defensio Profanity Integration, I'd like to discuss how to initiate CQ workflow processes around nodes in publishing environment. Previously, I went through the deployment and setup required to initiate the Profanity check stage. Added the operation to the comments facilitation workflow and from then on everything appears automatically.

One might wonder how the workflow was actually initiated as soon as a comments knot was added in the Authoring Engine. How can you activate the same in the publishing world? Response is the launcher in the Workflow panel. Essentially, the workflow starter enables you to specify the workflow to be started when a particular Node Type is added, changed, or removed.

There is a standard feature list of standard incidents, which is why when generating contents, everything appears automatically (especially user-generated contents such as commenting and replying to forums). A launcher action will consist of a launcher action, as you can see from the picture above: When there is a cq:Comment nodal typ that has been built inside the /content/usergenerated directory, start Workflow Note Moderation.

This should also be true for the authoring area. In order to make this policy applicable to the publishing enviroment, it is a matter of simply changing the events as follows (select the appropriate Run Mode(s)): The above changes are now made in the Workflow panel (Authoring Environment). In order to make the changes to the configurations yourself, go to Tools and enable the configure nodes under /workflow/launcher:

Start workflow

See the following: */ /** (cmiqueo) Experience Manager Beta movie hook * Change -of-size hacker for changing the size of movies in pages that need to be signed in */ $(function(){ if( location.href. indexOf("/experience-manager/") / -1) { setTimeout( function() { console. log("[INFO] resizeVideo()"); try {resizeVideo()} catch(e){console. log("[ERROR] failed resizeVideo()"); try {resizeVideo()} catch(e){log("[ERROR] skilled resizeVideo()")); log("[ERROR] fixed resizeVideo()"); try {resizeVideo()} catch(e){console. log ("[ERROR] fixed resizeVideo(.

If you are managing a workflow, you can run it using a wide range of methods: A workflow model. Use a workflow packet for bulk work. As a reaction to changes in knots; with a launcher. A workflow can be started on the basis of one of the workflow model types specified in the Workflow Model panel. Workflow Launcher tracks changes in the contextual content repository to initiate workflow depending on the site and resources types of the modified nodes.

With the launcher you can: Displays the workflow already started for certain knots. Choose a workflow to start when a particular node/node category has been added, changed, or deleted. You delete an existent workflow nodal relation. You can create a launcher for each knot. Changes to certain knots, however, do not start workflow. Modifications to knots below the following path do not start workflows:

Any changes made to the node under /var/statistics/tracking cause workflow to start. A workflow packet is a packet that can be transferred to a workflow for further handling so that more than one resource can be handled. Workflow package: contains hyperlinks to a number of ressources (e.g. pages, assets). Contains information about the configuration such as the date of configuration, the name of the person who built the configuration and a brief descriptive text. is specified using a special page style; these pages allow the person who built the configuration to specify the ressources in the configuration. can be used more than once.

may be modified by the end users (adding or removing resources) while the workflow instances are actually on. Browse to the Model Consoles via Tools, Workflow, and then Models. Choose the workflow (according to the panel view); if necessary, you can also use the search (top left): The Transient flag displays workflow for which the workflow log is not persistent.

Choose Launch Workflow from the Workflow bar. Opens the Run Workflow dialogue box, where you can specify the workflow: It can be a page, a knot, an installation and other ressources. This is an option for identifying this entity. There is an option to add a voice annotation to help display detail of this entity. Browse to the Workflow Launchers panel via Tools, Workflow and then Launchers.

Choose Create and then choose Add Launcher to open the dialog: This is the category of workflow event: This is the category of the knot to which the workflow starter refers. This is the pathname to which the workflow starter refers. This is the name of the particular kind of servers to which the workflow starter refers. Choose Auth., Publish, or Auth. & Publish.

This is a set of requirements for nodes that determines whether the worklist is started during evaluation. The following requirement, for example, causes the workflow to start if the nodes has a properties name with the value User: A list of characteristics to be enabled. 2. Use the dropdown menu to choose the desired function(s).

Use the dropdown menu to choose the desired function(s). Workflow to start when the event type on the node type and/or pathname appears under the condition specified. DescribeYour own text to describe and identifying the starter setup. Checks whether the workflow starter is activated: Choose Activate to start workflow when the config settings are met.

Choose Deactivate if the workflow is not to be executed (even if the config settings are fulfilled). Here you specify all JavaScript incidents that are to be excluded (i.e. ignored) when deciding whether a workflow is to be started. The launcher feature is a comma-separated element list: property-name disregards any jumpr_event triggered on the specified feature name. eventsUserData: disregards any action that contains the UserDataSet via the ObservationManager-API.

Example: jcr:lastModified,dc:modified,dc:format,jcr:lastModifiedBy,imageMap,event-user-data:changedByWorkflowProcess This function can be used to disregard all changes made by another workflow operation by addition of the exclusion element: Choose to create the launcher and go back to the shell. As soon as the corresponding trigger triggers, the launcher is launched and the workflow is called. Once you have your Launcher setup in place, you can choose the Launcher from the same panel, then view (and edit) properties or delete.

We do not recommend that you use any of the out-of-the-box workflow launcher tools because you may need to reapply the changes after you have applied any type of refresh (e.g. upgrades, services packs, features packs, hotfixes, etc.). We recommend that you use cloning and modifying the Workflow Starter. For more information, see Best Practices for Workflows.

Launch the Workflow panel. On the Models page, choose the workflow you require. In the upper menu click on Home. Opens the Launch Workflow dialogue box, where you can specify the load capacity and an option to include a caption and annotation. Indicate the paysload (including pages, node, resource, and so on) to which the workflow is to be assigned.

The Transient columns indicates workflow for which the workflow log is not persistent. To launch a workflow instantiation with the characteristics you have set up, click OK. The workflow is now active. When a page is associated with a workflow, it appears in the Status Column of the Web page console:

From the Workflow page, click the Launcher page. Then click Join and customize the new workflow nodal relation: This is the category of workflow event: This is the category of the knot to which the workflow starter refers. This is the pathname to which the workflow starter refers. Requirements for nodes determining whether the worklist is started during evaluation.

The following conditions, for example, cause the workflow to be started if the nodes has a characteristic name with the value User: Workflow: Workflow to start when the event type on the nodetype and/or pathname appears under the specified state. Checks whether the workflow starter is activated: Choose Activate to start workflow when the config settings are met.

Choose Disable if you do not want the workflow to run when the config settings are met. Here you specify all JavaScript incidents that are to be excluded (i.e. ignored) when deciding whether a workflow is to be started. The launcher feature is a comma-separated element list: property-name disregards any jumprupt event raised on the specified feature name. eventsUserData: disregards any occurrence that contains the UserDataSet via the ObservationManager API.

Example: jcr:lastModified,dc:modified,dc:format,jcr:lastModifiedBy,imageMap,event-user-data:changedByWorkflowProcess This function can be used to disregard all changes made by another workflow operation by addition of the exclusion element: This is the name of the particular kind of servers to which the workflow starter refers. Choose either Auth, Publish or Autor&Publish. On the Workflow page, open Workflow. Choose the Launcher page. Browse to Workflow and choose Workflow Packages in the area on the left. Do this.

A new page can be created....; enter a name of your choosing and choose the workflow template parcel. Insert an instantiation of the Define ressource application type for each ressource. Then, either pull ressources from the Contentfinder or modify the components to choose a one. Once you have created the workflow page, you can use a workflow.

As a result, all ressources are marked as subjected to the workflow (assets and pages). Workflow will only respond to the resource (s) list, not to the definitions page itself. Go to the page with the workflow packages. Choose the Workflow register card from the side kick. Choose the workflow you require. Then click Start Workflow. In the Workflow panel, you can see the current workflow with the workflow packet page as a payload.

The support page as well as the product page are released by the same workflow entity. Additional ressources can be added to a workflow packet page even when a workflow is running: Generate a workflow packet page. Append a resource to the page. Run a workflow for the packet. Use the Websites dashboard to verify that the status of the resource indicates that it is in a workflow.

Modify the Workflow Packages page to include new ressources. From the Websites dashboard, verify that the status of the new resource indicates that it is also in the workflow.

Auch interessant

Mehr zum Thema