nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Workflow to identify SitePublisher feature

shweta_komal

Hi,

In TeamSite 7.2.1. "default" content-store, we have 1 branch which has SitePublisher implemented & 3 branches where SitePublisher is not implemented.

We intend to write only one workflow, that will check if the branch (from which it is triggered) has sitepublisher or not. If YES, it'll do Task-A, if NO, it'll do Task-B.

P.S. Task-A = Task-B+ Task-X (SitePublisher/LiveSite-related-tasks)

Could you please confirm if it is possible to customize and place this "check" inside workflow?

If we can do this check for "SitePublisher-enabled-branch" in the workflow itself, we can save the effort of writing a 2nd workflow.

Find more posts tagged with

Comments

nipper

Yes you can do this

I typically use the PLC workflow and add additional targets (for non SP content). Then in the WF startup (custom_instantiation) I use FormAPI to determine which branch the job is starting from and which deployment beans are to be used.

shweta_komal

Hi,

Thank u for your message...

We intend to write the workflow in WFM. It would be a combination of PLC and customization based on our business process. I understand that u suggest, that we can use FormsAPI to make the check for which branch the *new* workflow is getting initiated from, and then perform a check on what deployment beans to be used.
1. Does it boil down to saying "using cssdk"?
2. Can we use the Deploy-and-run concept of OpenDeploy i.e. run a script to determine which branch we are initiating, workflow from and then run the workflow? (does this make sense?)

-Regards
Shweta