Form-centric workflow: How to implement a OSGi service for custom metadata (assign task) | Community
Skip to main content
Level 2
November 4, 2020
Solved

Form-centric workflow: How to implement a OSGi service for custom metadata (assign task)

  • November 4, 2020
  • 4 replies
  • 2670 views

Hello

Currently I'm working on forms-centric workflows. I'm using the assign task component and I need to add some custom values into the custom email templates. As per documentation (https://docs.adobe.com/content/help/en/experience-manager-65/forms/publish-process-aem-forms/use-metadata-in-email-notifications.html#use-an-osgi-bundle-and-java-interface-to-add-custom-metadata) I should be able to write my own OSGi service which prepares the metadata map.

Unfortunately I'm not able to successfully get the OSGi service listed in the field Assign Task --> Advanced --> Custom Metadata. It seems that the above linked documentation is incomplete (e.g. see point 4).

Was anyone able to create such a OSGi service and get it listed for selection? If so, is there a working example available?

Kind regards
Richard

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

4 replies

Level 8
November 4, 2020

I will send you a sample code soon

i have it somewhere on my laptop

Level 2
November 4, 2020
Great, thank you very much in advance!
GirishBedekarAccepted solution
Level 8
November 4, 2020
Level 2
November 4, 2020
Thank you very much! Can you also provide the necessary maven dependency?
Level 8
November 4, 2020

Let me know If you have questions on the link I sent you

we will update the other link as well

thanks

Level 2
November 4, 2020
When implementing the mentioned interface, I get asked to implement getUserMetadataMap(). Can you therefore also add the information regarding the needed maven dependency where the package with the interface is included? I assume, I'm working with an outdated version.
Level 8
November 4, 2020

Yes the versions are confusing. We are going to start naming the versions which are in sync with AEM forms release version

sorry for the confusion