Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Invocation method invokes which version of application

Avatar

Level 7

Hi,

Could anyone know me if i invoke a process using invocation method. Which version of application will get invoked.

Lets say , I have application as MYAPPLICATION and a process MYPROCESS, version of this application is 1.0.

when i deploy this application, i use MYAPPLICATION/MYPROCESS , and pass map parameter to it. So it invokes the process.

If i create one more version of thsi application let say 1.1

then my invocation method will invoke which version of application.

I am confused because we dont define any version in invocation api.

Will it call latest application?

Regards

Sunil

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Hi Sunil,

Yes it will call the latest deployed and active version of the process.

Regards,

Thomas

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

Hi Sunil,

Yes it will call the latest deployed and active version of the process.

Regards,

Thomas

Avatar

Level 7

@Thomas

Thanks for providing me information.

Regards

Sunil

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] ----