Expand my Community achievements bar.

Enhance your AEM Assets & Boost Your Development: [AEM Gems | June 19, 2024] Improving the Developer Experience with New APIs and Events
SOLVED

changin the process type

Avatar

Level 2

What are the implications or cautions when changing a short lived process to long lived process and vice versa?

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

If you change a short lived to a long lived without versioning it, any running processes will stall if they call it.  It will complain about not being able to start the process synchronously.

View solution in original post

2 Replies

Avatar

Former Community Member

The basic difference is that a short lived process does not store its process state in the LiveCycle DB the long lived processes do. So when you drop a user task on the process diagram it will change to a long lived automatically as the process data must be stored in the DB.

Make sense?

Paul

Avatar

Correct answer by
Former Community Member

If you change a short lived to a long lived without versioning it, any running processes will stall if they call it.  It will complain about not being able to start the process synchronously.

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----