Workflow definition not activated

Hi,
after transporting a workflow from DEV to QUA environment I get the following error message in transaction SWU0:
"Workflow definition not activated"
How can I solve the problem?
Thank you.
//Elvez

Hi,
Looks like your workflow template that is transported is not active. Check the workflow status in the Information Area on the top left in SWDD (below the wokflow template id). It shud be "Active, Saved". If it something else click on the "Activate" button.
I am not sure if you are allowed to do this directly in Quality. If not allowed try creating the WF template in a new request and try transporting again (U might get one more version generated in quality but this might solve your problem)
Thanks,
Prasath N

Similar Messages

Error in WS14000075: Workflow definition '' not in version ''

Hi,
We are getting the following error on our SRM 5.0 system while trying to approve the PO with 0step approval workflow: (in swud after running a consistency check on the workflow WS14000075)
E WD:401 Workflow definition '' not in version ''
We have already checked OSS Note 962488 and it did not resolve our problem. Besides we had a look at the forum Workflow without approval not working
Awaiting your help

Hi Emre,
In our case the problem was in several confirmation standard workflows.
In the workflow builder (SWDD) we use the navigation Area to check every workflow. I mean we did double click in each step, if the step had a subworkflow, then we open the subworhflow, checked it, and if it appeared the same error we used the function module for the subworkflow.
In this way we achieved to solve the problem. I hope this helps you.
BR.
Jorge

Recent Workflow Version not active in Production server

Hi Gurus,
Recently, I made a minor change to an existing workflow. After the changes, it was transported to QA and Production. In QA, the changes are reflected and when I click on the version overview tab of the workflow, I can see that my last changed version is the active version. But, In production server the last version is not active. The previous version before my changes remains as the active version. Though it shows my version their, it is not active and the change are not yet reflected.
To solve this I tried following ways,
1) I refreshed the buffer in SWU_OBUF in Production, but no improvements.
2) Then I tried to check, if there could be any errors when I activate the workflow in Development server. But, there are no errors except few warnings like some of the variables declared for the workflow but not used. So, this also does not help.
3) Then I tried changing the workflow to tag it again to a transport request thinking in a way, previously there might be a problem in attaching the active object. But, even after transporting the second changes, the workflow version is still not active in Production. But, it is active in QA.
Please let me know, if I can try any other ways which is not mentioned above!
Thanks a million.
AM

Hello,
Check the transport logs for any errors and make sure all the transports have been done, and in the right order.
What was the minor change that you made?
You can get situations like this when you eg create a task, don't transport the task, and then add the task to a workflow and transport the workflow. In Development all will be fine, but not so in QA and/or Production.
regards
Paultje Bakker
Hanabi Technology

Reg : workflow definition not defined

Hi ,
     I find issue with activating a custom workflow which i used before . Though it does not show any error in the templete,I could not activate them .When i diagonised the workflow it showed "Theworkflow definition is not defined " I had done done buffer refresh but still could not resolve. Please advice.
Regards,
Buddy.

Hello KumarShankar !
           Please check whether the version overview does show active version.
           If not, execute the function module SWD_WFD_REPLICATE_FROM_9999.In doing so, pass the workflow id to the import parameter IM_TASK in the format WSxxxxxxxx followed by refresh workflow buffers at SWU_OBUF transaction.
Regards,
S.Suresh

This is interesting..fonts showing properly when NOT activated

Version 10.0.0.70 of InDesign.
If I open a clients CC file I get no warning that the fonts are not active and they display properly.
While this can certainly be useful if the fonts are not provided it's also potentially dangerous.
I can package the file with out the fonts being packaged either. Without any warning that fonts will not be packaged.
In fact, I have seen customer files sent in without the fonts and it was clearly packaged.
I can also make a pdf with the fonts embedded.
If this is a feature, I should still be warned that "the fonts are not active but I will be able to see the fonts correctly in this window.
If I save as.. or copy and paste I will not see them properly". Or something to that effect
If however, this is not a feature, I would like to know how it's working. It is repeatable on every Mac here.
By the way, I DO NOT have type kit enabled.
Thanks for any input.
Jim

Mikey,
No, definitely not activated anywhere.
I control all the fonts and know exactly where they all are, which ones have to stay, which ones the OS tries to repair when moved even though they are not crucial, etc etc.
It's odd because, if as I mentioned above, if we "save as.." and then reopen the file, the dialogue box comes up alerting the user that the fonts are indeed missing.
Also, if I drag the font frame to a new window or copy and paste to a new document, I can see in "Normal" mode the fonts become highlighted in pink, indicating of course that the font is actually missing.
We can reproduce this on all the Macs here regardless of the font(s) being used.
I wish it was as simple as a font being activated somewhere.
Thank you for the attempt though.
Jim

Changes in Workflow is not reflecting

Hi,
I have created one workflow definition and activated and tested. After that I have changed the workflow definition and when I tried to test it again it is executing the old definition. I have tried executing the standard transactions SWU_OBUF and PPWFBUF. But it is executing the old definition. There is any transaction to correct this?
Kindly provide me a solution.
Thanks
Sujith

Sujith,
Problem might be becuase you might be trying to test in different client. You need to generate runtime version of the workflow in testing client also. Do the following:
Say your development client is - 100 and testing is on 200
Once your changes are done in 100, login in 200 open the same WF in SWDD and press Ctrl + F3.
It will work like a zoom..
Karthik C Sunil

Workflow definition of task 'WS90123456' cannot be activated

Hello Experts,
I am trying to activate a workflow on document event change, and i am getting this error in the event trace: Workflow definition of task 'WS90123456' cannot be activated
In the receiver data i have:
receiver type : ws90123456
object key:
receiver fm: SWW_WI_CREATE_VIA_EVENT_IBF
rfc destination:
check fm
receiver type fm:
message: Workflow definition of task 'WS90123456' cannot be activated
any ideas as to why this is happening ?
The workflow has no errors and it is being generated correctly with no warnings and no errors
points are awarded,
regards

Hi
Go to SWDD and activate the workflow template. Then go to SWU_OBUF and refresh the buffers, and then refresh the org environment using the option in SWUD-->Problem:Workflow Does not start menu path. Test your event again
If still no joy goto SWUD go to Test Environment and select simulate event taking note of the messages code displayed.
Regards
Gareth

Error : Workflow definition does not exits(T-code : SWU7 )

Hi All,
I checked my workflow template in SWU7 .Its gives me error "Workflow definition does not exits".
In the bottom left of screen it displays message : "Container Element ZBUS2081 is not used".
How can remove this error ? Please help..

Hi ,
The method used is standarad "GETEMAILDATA".
no changes have been done to this.
In bindings(exist)
Workflow Step 'Get data from Email'
&INCOMINGINVOICE.PAYMENTBLOCK& &PAYMENTBLOCK&
Then in Containers tab{ other tabs include basic data,description,triggering events,terminating events,defualt values,sapphone)
this expression have been defined :
abap dict. refernce : RBKP-ZLSPR
PROPERTIES : IMPORT,EXPORT and MANDATORY.
The BO name is ZBUS2081
For BOR ZBUS2081
bus2081.PaymentBlock datatype refernce : RBKP-ZLSPR
method defined :bus2081.BlockedPriceCheck
Kindly check if fine.
Edited by: ujjwal dharmak on Nov 22, 2010 9:14 PM

Regarding the Workflow definition 'WS10000051' not in version '0001'

Hi,
iam using the worklow template WS10000051 and when try to view the workflow builder it 's giving error " Workflow definition 'WS10000051' not in version '0001"
please let me know the solution!!
it's very urgent!!
thanks
ram

Prasath Natesan wrote:Did u check the URL provided by me in the previous post. Below is one of the responses in that thread!
>
>Are you in ECC 6.0? check note 981295 and the below message.
>
>incomplete / missing workflow on ECC 6.0
>
>Thanks,
>Prasath N
Check this note and also check out various other options provided by others.
Thanks,
Prasath N

Workflow definition of task WS92000077'' CANNOT BE ACTIVATED.

Hi Friends,
While i run material master workflow in Devlopment server its working.
But its showing erroe in Quality Server.
Workflow definition of task WS92000077'' CANNOT BE ACTIVATED.
Pls suggest
Moosa

Hello,
It could be that some objects that it relies on (eg tasks, sub-workflows) haven't been transported.
Are there any other error messages, eg saying something doesn't exist?
Did you try to activate it?
Also, as always, try SWU_OBUF.
regards
Rick Bakker
Hanabi Technology

Workflow getting de activated

Hi
I created a custom event 'ItemCreated' for object type MSEG.
However, whenever a item is created in MM transaction, the event is getting created which I can see in event trace but the workflow does not get triggered and event linkage gets deactivated as well in the workflow.
I am getting the following feedback in event trace:
Workflow definition of task 'WS91100019' cannot be activated
Please let me know how to fix this.
Regards
Waz

I'm wondering if at the time of triggering the ItemCreated event, if the data has been truly committed to the database.
I'm getting at what may be a conflict between the MSEG getting created in an Update Task and the point in time when the BADI is called.
If the BADI is called before MSEG gets committed that would cause a problem, though probably and OBJECT_NOT_FOUND exception.
First I would start the workflow using SWUS. If that works, then...
I would try triggering the ItemCreated event manually using SWUE, for the instance of MSEG that you got your most recent error. You know for certain that the instance was created earlier (just no wf started). If SWUE starts the WF, then the BADI call is suspect. If you still get the same error then its something else.
The Workflow Template itself is active from what you mentioned before correct? I would go back to the template, generate a new version, then activate it, and examine all the messages that come from activating it, looking for something suspicious
I would also create a new shell of a workflow (maybe a simple container operation step at most), with the same Event Linkage to ItemCreated and see if it starts.
I would also try deleting the binding between the Event Container and Workflow Container temporarily and retry just to see if the WF will start. Sure the flow will error without a leading object, but at least it would have started.
Keep me posted...

Issue with Inactive Approver Role in Workflow definition

Hi Experts,
we are having issue with Inactive Approver Role in workflow definitions.
we have created workflow for Master agreements and Projects. Phases and workflow are working fine.
But the issue is when a programmatically added approver has completed the approval activity, collaborator role is not changing from approver role to Inactive Approver Role mentioned in workflow definition. For example, you might select Reviewer in Inactive Approver Role, Then Selected collaborator role to be given to programmatically added approvers when the approval activity is completed.
This is functionality not happening when project or contract document approved and workflow completed in project and MA. we have followed all the standard functionality when we have created workflow. Please see screen shot for the same.
Can anyone please tell me is there any functionality we missed it or do we need to write any script in xpdl or do we need to check anything with collaborator role or with security profiles.
we have checked with other roles also same issue coming.
This Reviewer is in active state and have Readonly profile. We don't have Pre script in this workflow because we are using standard approval.
Thanks in advance!
Lava

Thanks gary for your helpful answer.
As per your answer We have added the approver role in the prescript so that it gets added programmatically , still no luck.
here is the script we wrote in prescript.
import com.sap.eso.api.common.*;
import com.sap.eso.api.projects.*;
import com.sap.odp.api.workflow.*;
import com.sap.odp.api.usermgmt.masterdata.*;
import com.sap.eso.api.doc.collaboration.*;
import com.sap.eso.api.doccommon.masterdata.*;
import com.sap.eso.api.ibean.*;
import com.sap.odp.api.ibean.*;
import com.sap.eso.api.contracts.*;
import com.sap.odp.api.doc.collaboration.*;
collaboratorsCollection = doc.getCollectionMetadata("COLLABORATORS").get(doc);
if (collaboratorsCollection.size() > 0)
   for (int i = collaboratorsCollection.size() - 1; i >= 0; --i)
        collaboratorsCollection_member = collaboratorsCollection.get(i);
        if (hasValue(collaboratorsCollection_member))
           collaboratorRole = collaboratorsCollection_member.getCollaboratorRole().getDisplayName();
            // Get approver of Role "Approver".
           if(collaboratorRole.equals("Approver"))
                principal = collaboratorsCollection_member.getPrincipal();
if (hasValue(principal))
     addApprover(principal);
Do you have any other suggestions? or if you have any related code snippet please share with us.

The workflow could not update the item, possibly because one or more columns for the item require a different type of information using Update Item action

I got error "The workflow could not update the item, possibly because one or more columns for the item require a different type of information "I found out the cause is Update Item action
I need to update item in another List call Customer Report ,the field call "Issues" with data type "Choice" to yes
then the error arise . please help..

Thanks for the quick response Nikhil.
Our SPF 2010 server is relatively small to many setups I am sure. The list with the issue only has 4456 items and there are a few associated lists, eg lookups, Tasks, etc see below for count.
Site Lists
Engagements = 4456 (Errors on this list, primary list for activity)
Tasks = 7711 (All workflow tasks from all site lists)
Clients = 4396 (Lookup from Engagements, Tslips, etc)
Workflow History = 584930 (I periodically run a cleanup on this and try to keep it under 400k)
Tslips = 3522 (Engagements list can create items here, but overall not much interaction between lists)
A few other lists that are used by workflows to lookup associations that are fairly static and under 50 items, eg "Parters Admin" used to lookup a partners executive admin to assign a task.
Stunpals - Disclaimer: This posting is provided "AS IS" with no warranties.

[Urgent] Error: The transaction is not active

Our process encounters some errors when the execution time takes longer than normal, e.g. 5mins. Any help is much appreciated.
Process Flow:
The flow consists of 3 process, 1 long-lived process and 2 short-lived processes, let say process A, B and C
Long-lived process A call short-lived process B,
and then, short-lived process B call another short-lived process C.
There is a loop inside process B, so that process C would be called several times.
* Both invocation policy have been tested, including "Do not wait for response" and "Wait for response".
Problem:
Everything work fine when the whole process is within a short-period of time. e.g. 1-2 minutes
However, when the process takes longer, e.g. > 5mins, we got some error message in the sever log.
Server log:
2011-08-18 18:43:11,625 ERROR [org.jboss.ejb.plugins.LogInterceptor] TransactionRolledbackLocalException in method: public abstract java.lang.Object com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterLocal.doRequiresNe w(com.adobe.idp.dsc.transaction.TransactionDefinition,com.adobe.idp.dsc.transaction.Transa ctionCallback) throws com.adobe.idp.dsc.DSCException, causedBy:
java.lang.IllegalStateException: [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] The transaction is not active!
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commit(TransactionImp le.java:223)
at org.jboss.ejb.plugins.TxInterceptorCMT.endTransaction(TxInterceptorCMT.java:501)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:411)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor. java:138)
at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648)
at org.jboss.ejb.Container.invoke(Container.java:960)
at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:430)
at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:103)
at $Proxy167.doRequiresNew(Unknown Source)
at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:143)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor.intercept(TransactionInt erceptor.java:72)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.InvocationStrategyInterceptor.intercept(InvocationStra tegyInterceptor.java:55)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.InvalidStateInterceptor.intercept(InvalidStateIntercep tor.java:37)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.AuthorizationInterceptor.intercept(AuthorizationInterc eptor.java:188)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.JMXInterceptor.intercept(JMXInterceptor.java:48)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.engine.impl.ServiceEngineImpl.invoke(ServiceEngineImpl.java:115)
at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:129)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.routeMessage(AbstractMessage Receiver.java:93)
at com.adobe.idp.dsc.provider.impl.vm.VMMessageDispatcher.doSend(VMMessageDispatcher.java:20 9)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispat cher.java:66)
at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)
at com.adobe.workflow.engine.PEUtil.invokeAction(PEUtil.java:886)
at com.adobe.workflow.engine.SynchronousBranch.handleInvokeAction(SynchronousBranch.java:510 )
at com.adobe.workflow.engine.SynchronousBranch.execute(SynchronousBranch.java:888)
at com.adobe.workflow.engine.ProcessEngineBMTBean.continueBranchAtAction(ProcessEngineBMTBea n.java:2792)
at com.adobe.workflow.engine.ProcessEngineBMTBean.asyncInvokeProcessCommand(ProcessEngineBMT Bean.java:697)
at sun.reflect.GeneratedMethodAccessor1076.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.invocation.Invocation.performCall(Invocation.java:359)
at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionConta iner.java:237)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionI nterceptor.java:158)
at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121)
at org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext(AbstractTxInterceptorBMT.java:1 73)
at org.jboss.ejb.plugins.TxInterceptorBMT.invoke(TxInterceptorBMT.java:77)
at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstance Interceptor.java:169)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor. java:138)
at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648)
at org.jboss.ejb.Container.invoke(Container.java:960)
at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:430)
at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:103)
at $Proxy200.asyncInvokeProcessCommand(Unknown Source)
at com.adobe.idp.workflow.dsc.service.ProcessCommandExecutorService.invokeProcess(ProcessCom mandExecutorService.java:55)
at sun.reflect.GeneratedMethodAccessor3010.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.adobe.idp.dsc.component.impl.DefaultPOJOInvokerImpl.invoke(DefaultPOJOInvokerImpl.jav a:118)
at com.adobe.idp.workflow.dsc.invoker.WorkflowDSCInvoker.invoke(WorkflowDSCInvoker.java:154)
at com.adobe.idp.dsc.interceptor.impl.InvocationInterceptor.intercept(InvocationInterceptor. java:140)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.DocumentPassivationInterceptor.intercept(DocumentPassi vationInterceptor.java:53)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor$1.doInTransaction(Transa ctionInterceptor.java:74)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(EjbTr ansactionCMTAdapterBean.java:357)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doSupports(Ej bTransactionCMTAdapterBean.java:227)
at sun.reflect.GeneratedMethodAccessor298.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.invocation.Invocation.performCall(Invocation.java:359)
at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionConta iner.java:237)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionI nterceptor.java:158)
at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstance Interceptor.java:169)
at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:378)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor. java:138)
at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648)
at org.jboss.ejb.Container.invoke(Container.java:960)
at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:430)
at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:103)
at $Proxy167.doSupports(Unknown Source)
at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:104)
at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor.intercept(TransactionInt erceptor.java:72)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.InvocationStrategyInterceptor.intercept(InvocationStra tegyInterceptor.java:55)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.InvalidStateInterceptor.intercept(InvalidStateIntercep tor.java:37)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.AuthorizationInterceptor.intercept(AuthorizationInterc eptor.java:165)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.interceptor.impl.JMXInterceptor.intercept(JMXInterceptor.java:48)
at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
at com.adobe.idp.dsc.engine.impl.ServiceEngineImpl.invoke(ServiceEngineImpl.java:115)
at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:129)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.routeMessage(AbstractMessage Receiver.java:93)
at com.adobe.idp.dsc.provider.impl.vm.VMMessageDispatcher.doSend(VMMessageDispatcher.java:20 9)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispat cher.java:66)
at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)
at com.adobe.workflow.engine.PEInvokeProcessCommand.execute(PEInvokeProcessCommand.java:126)
at com.adobe.workflow.workadapter.WorkflowCommandExecutionUnit.execute(WorkflowCommandExecut ionUnit.java:22)
at com.adobe.idp.dsc.workmanager.adapter.ManagedAsynchronousWorkAdapter.run(ManagedAsynchron ousWorkAdapter.java:70)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
at java.lang.Thread.run(Unknown Source)

Hi Paul,
Thank you for your advice.
It seems that it is not a bug of Adobe Livecycle, but some kind of configuration problems. Since the problem does not occurs when the process implementation time is short, such as 1-3 minutes.

How to run Assignment in Series - Workflow can not connect two Assignments

Here is my scenario:
I have a custom repository with no Taxanomy table.
I want to run series of Assignments.
I defined 5 assignments.
Thought that I can use MDM Workflow to call them in series. However MDM Workflow does not let me connect one Assignmen Task to next Assignment Task.
How to run Assignments in Series, either using Workflow or by using someother mechanism.
Idealy it could have been nice to Group the Assignments like Validation.
Or even Much better powerful Assignment and Validation Script. Add "Script Documentation" to that please.
Thanks,
Abhay

I tested with 2 assignments.
I created 2 assignments.
My workflow definition has a Start, Assign1, Assign2, Stop.
Start -> Assign1
Assign1 -> Assign2
Assign2-> Assign3
They are connected in Series.
Make sure all the steps are connected properly.
I executed the workflow and the two fields in the table got the assigned values as the result of the workflow.
Check the version of your Data Manager. The DataManager I used to test this is of version 5.5.34.26.
A single workflow should suffice for your requirements.
However, there is a workaround for this.
You create 5 workflows each with a single assingment step.
For the <b>Stop Step</b> in the Workflow you have <b>Launch</b> Property.
In this case, for workflow1 you set the launch property to Workflow2.
For workflow2 set the launch property as workflow3.
This way you are calling separate workflows sequentially.

Workflow definition not activated

Similar Messages

Maybe you are looking for