I am able to extract the implementation. Just adding for everyones
reference-AEM Version: 6.5.10serviceId = 5349, bundleId = 329Fetch the
bundle jar from this location :
/crx-quickstart/launchpad/felix/bundle/version/bundle.jar
package : com.adobe.cq.dam.cfm.impl.uiClass name :
EnumerationOptionsRenderDatasource
Thanks @Shiv_Prakash_Patel This worked for me. Finally the solution am
following is I am not adding any static options while constructing the
model. This do not create optionsMultifield node. This will just create
datasource node beneath the item node.As explained in the article share
by you, I have created acs commons generic list configurations and am
referring the same to be used in datasource resourcetype and path.Again
thanks for such a descriptive and clear solution
@dan_klco , thanks for sharing. I went through the blog, it gave me a
fair idea of overall concept. However, can you please provide more
details around how the content fragment dropdown element be connected to
the acs aem commons generic list components
Hi @manisha594391 ,Sharing code snipped. Try to use Junit5 and aem
specific frameworks to write unit tests. try to use AemContextExtension
and MockitoExtension if needed@ExtendWith({AemContextExtension.class,
MockitoExtension.class})Sharing code snippet for schedulerTest for run
method. Please check complete working demo files in
git.Scheduler@Component(immediate = true, service =
Runnable.class)@Designate(ocd = SchedulerConfiguration.class)public
class GeeksScheduler implements Runnable { priva...
The thing is, its the workitem created for dynamicparticipant step,
theat need to be uopdated with prop "ORIGINAL_PARTICIPANT", to be the
value of group, it was assigned to initially. so that the dropdown for
delegate is populated with group members
I am using uber jar 6.5.0. With that new XSSFWorkbook(inputStream) is
working fine runtime and am able to generate excel, however the same is
failing in PowerMockRunner junit with exception
org.apache.poi.POIXMLException:
java.lang.reflect.InvocationTargetException. Any pointers appreciated
Implementation for filtering/sorting is hidden in Granite Workflow API.
So we will not be able to arrive at what other columns/property can be
used for sorting. This is the reason why I mentioned Customization for
this use case is like rewriting the implementation.
Thanks @arunpatidar !! Combining below with other click events on load
of aem inbox, I am successfully able to populate the payload path and
get the filtered result.