Workflow Condition Step Failing

Hi All,
I am facing a very peculiar error.
I have two outcomes modelled depending on a varible (Material Type) in the worklfow.
My workflow gets triggered when I push SUBMIT button on my ADOBE interactive form on ABAP Web Dynpro launcehd
from UWL. Now if i check the workflow container, the variable is set properly. But still the condition fails. A backgorund task
having import parameters as Owrkflow container elements fails with an exception even though the import parameters are set.
But yes, again the workflow container same elements can be displayed on any form in further steps by reading the container
from ABAP webDynpro launched from UWL. Peculiar !!!
The same workflow works fine if I directly set the variables and test the workflow.
Why this ?..... Any Idea.... ? If something is written on to the workflow container can the workflow work on those variables ?
Please suggest.
Thanks & Regards,
Deb

Hi Rick,
Thanks for your suggestions. Actually we could solve it ina different way. It was a nice but tricky error in muy coding.
Here is what I was doing:
1) I tirgger my workflow on click of 'SUBMIT' button on my ADOBE interactive in AWD
2) Then I get the instance of the workflow to get the Workflow Work Item ID
3) Now I write the form data to the workflow container.
Note: By the time I write to my container, my workflow had been already triggered, with the condition step at the 1st.
And the container is not yet written, hence the condition fails.
Solution: I used a wait step. And Read the workflow container in loop untill the container elements are populated.
Once out of this loop, I now tirgger the write to the container and raise the wait event.
Cheers !!
Deb

Similar Messages

Condition in condition step type always fails

Hello all !
        I've a condition step type in workflow.
        The condition is as follows :
                       &ZBUS2011.REQ_TYPE& = 0001 AND &PLANT& = X
        The containers in workflow log is populated with required values. However, the above condition fails for no reason.
        More over, on clicking "Evaluation condition with test data" button in condition display window, a pop-up message " The evaluation of the condition gives the result 'False' "appears.
        Whether this could be the cause ? How to make the result 'True' ?
        Any suggestion most welcome.
Regards,
S.Suresh.

Hi Suresh,
Is your attribute ZBUS2011.REQ_TYPE a vitrual attribute ? If so please check if the attribute is getting re-calculated during runtime. You can check this by instantiating the BOR and check initial value and then click on refresh button and see if the value has changed.
Thanks,
Ajay Bose

Regarding failuare of conditions step in Workflow.

Hi,
My workflow activity step calls webdynprofunction module.After screen is approved control goes back to workflow and condition statement immediatly below activity step get executed.However this condition always fails ie even after approving and getting approve value in container, reject branch of condition gets always executed. can anybody provide me solution?
Thanks & Regards.

Hi Sanjay,
Many have come across this situation earlier and couldn't really find out why this happens.
I would suggest that you delete the condition step and recreate it. Also clear the buffer using SWU_OBUF and see if it helps.
This is what i did when i faced this issue and helped.
All the best.
Regards,
Raj

About case and switch in multiple condition step in workflow.

i ve some information about case and switch in multiple condition in workflow.
case - static determination
switch - runtime determination.
but i want brief explanation about case and switch and difference please help me.....

hi velmurugan............
    in case,
           we can have only one value for comparison and can have any number of branches for it.
   in switch,
           we can compare any number of values and have any number of branches.
eg:
     consider i am triggering a workflow for purchase order change and i am having a multiple condition step.
if i am going for a case:
        i can have only on value (ie po number/vendor number.....) as a parameter and can check different values with it. ( eg vendor number < 1000
                                                             vendor number > 1000.... so on)
        a branch will be created for each condition.
if i am going for a switch:
        i can take any parameter needed. (eg: vendor number > 1000
                                                                order type = 'NB' .... so on)
         so a single branch can have any number of comparisons with the help of 'and' and 'or' operators and i can have any parameter for my condition.
---regards,
   alex b justin

Issue with Condition step in workflow

Hi Guys,
I am using a condition step to check the value of a variable A. If the value of A is 7 , then the wf will follow the true branch. If not it will go down the false branch. This is as simple as that. But the wf was going down the wrong path when i tried to test it. Meaning even if the value of A is 7, it was going down the false branch.
So i simulated that condition in the editor and manually entered a value of 7 for A and still it is going down the false branch.
I havent seen this issue before. Have any of you? I ahve tried clearing buffer, creating new version of the wf. But nothing has worked. I even tried to reverse the condition check. Like i tried to give IF A not equal to 7. Still its going down the worng branch.
Any ideas? The variable if declared of the type SYST-PEXPI. And the funny part is this wf is working fine in production.
Harish

Hi Harish,
Sometimes it happens that the value of the variable is not yet populated when the workflow is at the COndition step. Hence it always follow the same path irrespective of the actual value that needs to come.
Please check if the container element you are checking is having the correct value when at the COndition step. Else you can try adding a wait for few seconds step before the condition step and then test.
I guess the performance of the Production system is better than the dev or quality system so you are not facing the issue there.
Regards,
Saumya

By publishing this workflow, conditions and actions inside Impersonation steps will run using your credentials

In a SharePoint 2010 workflow that accesses a custom list, I am getting the following warning message before I publish the workflow to the SharePoint test server:
"By publishing this workflow, conditions, and actions inside impersonation steps will run with your credentials".
The only step in this SharePoint 2010 workflow is the impersonate step.
Thus would you tell me what I can do to have the workflow run under different credentials?

Hi,
As the warning says, any actions within Impersonation step would be carried out under your credentials if you published the workflow. If you intended to just add a Step in the workflow, then use different icon that says Step (with down arrow). Impersonation
step is used to modify the permissions on the item.
Once you have this, the workflow will be executing under the credentials of whoever starts it. Hope it helps.
Regards, Kapil ***Please mark answer as Helpful or Answered after consideration***

Workflow conditional statement not working

I have 2 level approvals of objects in Documents list.
The document first uploaded by user and then first need to get approval from HR Line Manager and then get approval from HR manager.
the attach image shows shows workflow , the issue is either I select approve or reject in first approval the if statement is always true , it should not go inside if statement if first approval is rejected by HR Line Manager roles
Tech Learner

Hi,
To make the condition work in the workflow, there are two more things need to be done:
1. Enable content approval in the Documents library which the workflow is associated with.
Go to the Library Settings page of the Documents library > click Versioning settings > select Yes under Require content approval for submitted items.
If we do not enable this, the value of Approval Status column will always be Approved.
2. Add a Set Workflow Variable step above the Start Approval Process step and set it to Yes in the workflow.
After adding the Set Workflow Variable step, we can set the Approval Status column when we approve or reject the task process. Otherwise the Approval Status column will not change no matter how the task process works.
Thanks,
Victoria
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Victoria Xia
TechNet Community Support

Assign values in condition step

Hi Friends..
iam creating container attribute refering standard structures..
and use that attributes in conditional step...
whenever iam executing the workflow it shows an warning message like this.
"container element is read purpose only.no values are assigned to it"
at the execution time this step was not working.. so what is the actual problem.. how can ihandle this
Thanks
Gowrishankar

I think You are creating attribute in Business Object. If you are doing so then create another container element in the Wflow and do a container operation of assigning the Attribute to this elelement. Please note that the Element type should match. I hope it is not a Multiliner. Use the container element which has been assigned the Attribute value in the Condition Step.
<b>Reward points if useful</b>

Multi Condition step

Hi,
I am changing the approval custom worflow.
In my workflw intial two step are MULTI CONDITION for plant and condition types.
previously we have used different approval procedure for different plant.
now all plants are having the same procediure.
so i am planning to remove the first MULTI CONDITION step.
when I removed that step workitem is not creating and workflow error.
binding problem error showing in one of the step in container.
pl help.
other wise it it possible to use the same procedure fordifferent plant with out creating new steps.
Thans in advance
sharma
Edited by: sharma on Sep 10, 2009 5:43 AM

Hi Sharma,
I have noticed with my workflows that often when you add or delete a task in a workflow, the bindings of other steps are also affected.
In your case, the binding of some other step could have got disturbed because of deletion of the multi condition step.
I would suggest you to create a new version of the workflow and compare your workflow after deletion of the step with the previous version. Check the bindings at each step.
Hope this helps!
Regards,
Saumya

Condition step expression comparison

Hi all,
I want use a condition step to check acondition like lv_expression1 = lv_expression2.
but i am not able to use variable in expression2, it's accepting as constants.
How to compare two variables in workflow?
Thanks.

It should be possible in the condition editor. First double click the first container element. Then set for example '='. Now double click another container element (don't put anything into the constant field). => You have comparison between two container elements.
Regards,
Karri
Edited by: Karri Kemppi on Dec 13, 2011 5:07 AM

Condition step

Dear Friend,
How to check whether a variable is initial or not in condition step type.
Thanks & Regards,
Arti

Usually the Not exist option also works. But why didn't you just try some things? It is not that hard to make a simple workflow with a condition and try out some option in the condition. I even think you would have had your answer sooner and also it would teach you something about the options you have in the condition.
Regards,
Martin

Workflow start step performs Exclusive checkout

We need to upload data to records that are in workflow and checked out by the workflow start step. Unfortunately the workflow start step performs an Exclusive checkout of the record which means that the background MDM Impor Server user cannot automatically join the checkout, the user first needs to be invited to the checkout, which needs a manual step of modifying the join permissions of the checkout, which is not what we want to do.
I have also noticed that when an existing record is checked out Exclusively the user's roles are pulled through into the permitted roles section of the join permission screen of the checkout. When a new record is checked out Exclusively the user's roles are not pulled through to the permitted roles section of the join permission screen of the checkout. This looks like a bug to me.
We are using MDM 7.1 SP08.
Please advise any workarounds to this problem. I can think of a few, but none are very elegant, e.g.:
1. Use API to invite import user to checkout before import is started (requires coding)
2. Get the user that owns the workflow to manually invite the import user (not guaranteed to remember)
3. Complete workflow and stat new wokflow without chekout before import is started.
Any advice will be appreciated.

Hi Johann,
I got you point.
Its not a bug in MDM these are the constraints in MDM :(.
To understand more read section CHECKOUT AND WORKFLOW FAILURE CONDITIONS of the import manager refernce guide.
http://help.sap.com/saphelp_nwmdm71/helpdata/en/4b/72b8e7a42301bae10000000a42189b/MDMImportManager71.pdf
In our lanscape we too have a scenario where we are creating/ records in MDM leaving Material Number Blank (Record Add workflow).
But once this record with balnk Material Number is syndicated to source system we stop this workflow.
Now from source system through change pointer we get a file immediately with material Number and MDMID.
which we process through MDIS and trigger another workflow(Record Import)
I guess this matches with the third option you described to start and stop workflow and trigger import.
Regards,
Neethu Joy

Creating Job with CmdExe Step failed with error Reason : 5

Hi, I setup a job with Type = Operating System (CmdExec) and Run as 'SQL Server Agent Service Account' , it failed to run with Message below :
Message
Executed as user: PROD\sqlserveragent. The process could not be created for step 4 of job 0x5A83AE4A12AEF649888E85F4072604F6 (reason: 5). The step failed.
1. I couldn't find what is meaning of Reason 5 here.
2. This step used to work previously and it 'not working' suddenly these few days. I wondering anyone make the changes but I am not able to trace it. Any guide to troubleshoot would be helpful.
Thanks .

Operating System ... (reason: 5). The step failed.
Operating System Error code 5 = Access denied, seems to be a permission issue.
Olaf Helper
[ Blog] [ Xing] [ MVP]

Job scheduling error : The return value was unknown. The process exit code was -1073741819. The step failed.

I am working in Sqlserver 2008 R2, SSIS 64 bit version
I am getting the below error while scheduling the job in the development server Database.
The return value was unknown. The process exit code was -1073741819. The step failed.
The SSIS front end execution runs fine.
Have anyone faced this issue before?

Hi Venkat,
If you already changed to 64bit and still doesn't work then create proxy account..
To create a proxy account
In Object Explorer, expand a server.
Expand SQL Server Agent.
Right-click Proxies and select New Proxy.
On the General page of the New Proxy Account dialog, specify the proxy name, credential name, and
description for the new proxy. Note that you must create a credential first before you create a proxy if one is not already available. For more information about creating a credential, see How
to: Create a Credential (SQL Server Management Studio) or CREATE CREDENTIAL (Transact-SQL).
Check the appropriate subsystem for this proxy.
On the Principals page, add or remove logins or roles to grant or remove access to the proxy account.
Thanks

Any ideas on a cleaner way to write this? - run through a function with multiple steps; if any step fails, restart the function from the begining

Basically there are 3 different functions for various "tests"; they each return "1" if the test passes and "0" on failure. A "master" function calls these 3 functions in the desired order and keeps a counter
of tests that pass. The counter has to be 1 to proceed to step 2, has to be 2 to proceed to step 3, and when it's 3 the loop closes.
This approach is giving the expected results, but I was wondering if anyone has ideas on a cleaner approach? What I really wanted to accomplish was to have the 3 tests past in succession and to provide an overall pass and proceed to the next step;
and also to exit the function if any step fails rather than running through each step before trying again. If the script were to for example loop through the 3 tests and wait until each one passes, tests 1 and 2 might pass, but then 3 might fail
a few times and finally pass before the script exits. I did not want to allow for that scenario to count as an overall pass.
Function Test1 {
If PASS Return 1
If FAIL Return 0
Function Test2 {
If PASS Return 1
If FAIL Return 0
Function Test3 {
If PASS Return 1
If FAIL Return 0
Function TestAll
[int]$counter = 0
$Check1 = Test1
If ($check1 -eq 1) {$counter++}
If ($counter -lt 1) {Exit}
Start-Sleep -s 15
$check2 = Test2
If ($check2 -eq 1) {$counter++}
If ($counter -lt 2) {Exit}
Start-Sleep -s 15
$check3 = Test3
If ($check3 -eq 1) {$counter++}
If ($counter -lt 3) {Exit}
Return $counter
Do {$STATUSCOUNT = TestAll}
While ($STATUSCOUNT -lt "3")

This is cleaner:
Function Test1 {
If PASS Return 1
If FAIL Return 0
Function Test2 {
If PASS Return 1
If FAIL Return 0
Function Test3 {
If PASS Return 1
If FAIL Return 0
Function TestAll{
while($true){
while($true){
$counter=0
if(($counter+=Test1) -ne 1){break}
if(($counter+=Test2) -ne 2){break}
if(($counter+=Test2) -ne 3){break}
return
Write-Host ('try again' + $counter) -fore
TestAll
Of course all of your test functions have syntax errors.
\_(ツ)_/

Workflow Condition Step Failing

Similar Messages

Maybe you are looking for