You are viewing limited content. For full access, please sign in.

Question

Question

Get Metadata From Profile keeps changning

Workflow
Updated April 27, 2021
asked on August 1, 2019 • Show version history

I published Workflow B by exporting the existing Workflow A then importing back with a different name. 

In the import wizard, I have changed the connection profile to point to a different repository for this workflow. 

However, every time I run the workflow B, it also triggers Workflow A.

So I went to Workflow Rule Manager and noticed that Workflow A's Get Metadata From has flipped to Workflow B's profile. Conversely, When I changed back Workflow A's Get Metadata From profile to the correct one, Workflow B's profile is flipped to Workflow A's profile and not sure why this is happening.

Any feedback is appreciated.

0 0

Answer

SELECTED ANSWER
replied on August 1, 2019

Rules don't have connection profiles. Each repository event is checked against all existing rules for that event type. If you don't have conditions excluding a specific repository, then, yes, an event from repository A can trigger workflows that are expected to work on repository B.

The connection profile in the starting rule wizard is provided as a convenience for picking fields and tags. It does not imply the rule will be tied to that repository.

0 0
replied on August 1, 2019

Thank you very much, Miruna. 

Your explanation makes total sense.  I had a misunderstanding about what the connection profile was used for in the starting rule. 

After adding the rule to specify the repository, A and B workflows are no longer being triggered simultaneously.

0 0

Replies

replied on August 27, 2019

Miruna,

 

Despite sounding logical, I am getting the same results as Aya. 

I created a workflow for HR The library wanted the same functionality so I exported the HR Workflow, imported it, renamed it and published it. After it was published,  I changed the connection profile in the new workflow itself to reflect the workflow credentials for the Library and published it. I then created the starting rules for the Library Workflow changing the 'get metadata from' drop down from HR the HR profile to the Library profile and published it. However, this action caused the staring rules 'get metadata from' section for the original HR Workflow to change to the Library repository and both workflows run when one is triggered as both repositories have the same setup.

 

I am running LF Workflow 10.2.1.113 on a Virtual Windows Server 2016 machine.

replied on April 27, 2021

Just for the record - I came across this same behavior, I have two workflows where changing the "Get Metadata from" on the starting rule changes the value for both.  I've exported the workflows, deleted them and the connection profiles.  Recreated the connection profiles and imported the workflows back in and still have the same issue.  I had to add conditions for specific repositories to keep the workflows from triggering to the wrong repository.  I have Workflow 10.4.3.139.

0 0
replied on April 27, 2021

Again, the connection profiles on the workflow definitions don't have any bearing on what you see in the drop-down in the starting rule wizard. Rules do not have a connection profile. The connection profile drop-down in the starting rule wizard is provided as a convenience for picking fields and tags.

0 0
replied on April 27, 2021

Regardless - they should be independent.  Changing on one rule should not change another.

 

0 0
replied on April 27, 2021

It is the last connection profile you used. It has no tie to the rule.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...