setting an activity as default start

i have a DQL ibound initiate as a parallel activity to my default initiate activity in the workflow. however when i install my workflow and run it, it goes to the initiate activity first which causes my workflow to fail as the main logic is written in the DQL inbound initiate. how do i make this as the starting point for my workflow so things roll out from there ?

thanks,

Raj

Find more posts tagged with

Comments

CláudioGil

Can't you define something like this:

If the start activity is triggered when all inputs are received then it will wait for the DQL Inbound, I believe.

Raj_K

hi claudio - this is the way my current workflow is set up. but i am unable to get the DQL inbound to kick off after the initiate activity has triggered off. it goes directly into Activity 2 without waiting for the DQL inbound to kick off.

i am able to get this to work that way in the debug mode but not when i deploy and launch via webtop.

thanks,

Raj

mszurap

Hi,

Have you set up the Activity-1 to be triggered even if only one input port is selected? (Trigger tab)

Raj_K

hi miklos - i think i am missing this setting, and this might be the way. i will check this setting. just curious to find out if there is an configurable way to say that i am only expecting inputs for activity 1 from a specific input flow (the DQL inbound in this case) ?

thanks,

Raj

Raj_K

one other thing i have noticed is that --> i select the "All input flows selected" option in the "trigger" tab of the decision split activity, and save and validate the template, when i check the the activity template, the setting flips back to the original "this number of input flows select:" option. not sure why this happens .. any help will be great.

thanks,

Raj

mszurap

Hi,

You shouldn't modify the activity template but the "Decision split" activity in your workflow template. Set it to "This number of input flows selected: 1".

As far as I know, you must define at least one Initiate activity in your workflow template, so this is fine as you just designed it. If you don't want to allow the users to start this workflow template, then try to revoke their grant on it (maybe read is enough to participate? They would need relate to start it).

CláudioGil

I've seen that behavior before (changing from all to 1 in the activity's trigger) . I'm not sure why this happens but try to ensure all paths are connected to the initiate activity. Try replacing the DQL initiate with a DQL step and creating a "no op" auto activity before the split. This way the split's trigger won't reset and it will wait for the DQL step.

Raj_K

hi miklos -

the setting i have made is to the decision split activity (screen shot 2) the moment i save, validate and install, i see that it flips back no matter what setting i make on the trigger tab (btw i also tried "this number of input flows select:" and set it 2 as i am having two initiate activities but upon install this again flips back to value 1).

Claudio -

did you try validating the workflow in the way you suggested, coz having a DQL inbound after the initiate did not work, as logically an initiate activity cannot be connected to another inbound initiate as both are technically looked as sources for data in the workflow, and the validation will bomb. instead i tried having another auto activity in my workflow between the first decision split and the two initiates, and tried setting the trigger tab on that to "All input flows as selected" i had the same issue again.