Customizing activity plan step edit dialog with a picker

[John]

We’ve added a user person picker to ActivityPlanTemplateStepDetail.dialog and seeing strange behavior. This is a nested dialog so this may be related to the issue.

1. If we pick a person press ok, then save the base dialog it works as expected
2. If we re-open the APT edit then the step edit dialog after step 1, the picked person is correct
3. If we open the step edit dialog then pick another person, press ok, (don’t save the base dialog) then reopen the step edit dialog the picker only has the single value from step 1.

In other words, it seems like the picker is ignoring the dirty state. Is this a known issue or are we doing something wrong?

This doesn’t happen when creating an APT, it only affects edit. Also noticed that the doc mgr table saves immediately when closing the nested dialog. That is inconsistent with other fields but probably an acceptable workaround. Is there a way to turn this on for a picker?

0

[Nicholas Mc Neilly]

We haven’t seen this issue with user pickers in that particular dialog (Assign To…specific user; For…related entity).
Please let us know what customization was made. The collection must be non-lazy but it should already be non-lazy unless forced.

0

[John]

I realized it’s a MultiPicker rather than a Picker (we need to select multiple in this case) – that may be the difference. I also turned off lazy in the Multipicker but that didn’t help – is that the place it should be turned off?

Here’s what was customized:

I added this layout referenced from ActivityPlanTemplateStepDetail.dialog

<Layout caption="idsf.ActTemplateSignatories.Signatories" class="ActivityPlanStep"> <Composite name="tblRootLayout"> <Multipicker attributes="(entity fullName)" caption="idsf.ActTemplateSignatories.selectSignatories" captions="fullName" head="true" icons="icon" items="(@ signatories)" lazy="false" mode="ActivityPlanStep signatories" name="signatoriesPickerMM" ref="mda:UserPerson" /> </Composite> </Layout>

1 2 3 4 5

<Layout caption="idsf.ActTemplateSignatories.Signatories" class="ActivityPlanStep">    <Composite name="tblRootLayout">       <Multipicker attributes="(entity fullName)" caption="idsf.ActTemplateSignatories.selectSignatories" captions="fullName" head="true" icons="icon" items="(@ signatories)" lazy="false" mode="ActivityPlanStep signatories" name="signatoriesPickerMM" ref="mda:UserPerson" />     </Composite> </Layout>

Here’s the line from UserPerson.picker:

<Mode factory="bgm:ActivityPlanStepSignatory create" name="ActivityPlanStep signatories" selection="ActivityPlanStep signatories"/>

1	<Mode factory="bgm:ActivityPlanStepSignatory create" name="ActivityPlanStep signatories" selection="ActivityPlanStep signatories"/>

Here’s the ActivityPlanStep.meta attribute

<Attribute collection="true" name="signatories" reverse="step" type="bgm:ActivityPlanStepSignatory"/>

1	<Attribute collection="true" name="signatories" reverse="step" type="bgm:ActivityPlanStepSignatory"/>

Here’s the new class bgm:ActivityPlanStepSignatory. I expect it to be reproducible without persistence but I haven’t tried but let me know if you want datasource/upgrade too.

<Class description="BGM: A participant in batch printing: specifies signatories."> <Attributes> <Attribute name="entity" type="UserPerson"/> <Attribute description="The associated step." name="step" required="true" reverse="signatories" type="ActivityPlanStep"/> <Attribute name="fullName" type="string" value="(@ entity fullName)"/> <Attribute name="icon" type="string" value="(@ entity icon)"/> </Attributes> <Events/> <PersistenceMapping dataSource="DefaultRelationalDatabase"> <RelationalMapping keyGenerator="KeyGenerator.GUIDGen" primaryTable="ActivityPlanStepSignatory"> <AttributeMappings> <AttributeMapping destinationKey="UserPerson.PK" name="entity" sourceKey="APStepSignatory.PK.FK_UPrsn"/> <AttributeMapping destinationKey="ActivityPlanStep.PK" name="step" sourceKey="APStepSignatory.PK.FK_Step"/> </AttributeMappings> </RelationalMapping> </PersistenceMapping> </Class>

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

<Class description="BGM: A participant in batch printing: specifies signatories.">    <Attributes>       <Attribute name="entity" type="UserPerson"/>       <Attribute description="The associated step." name="step" required="true" reverse="signatories" type="ActivityPlanStep"/>       <Attribute name="fullName" type="string" value="(@ entity fullName)"/>       <Attribute name="icon" type="string" value="(@ entity icon)"/>    </Attributes>    <Events/>    <PersistenceMapping dataSource="DefaultRelationalDatabase">       <RelationalMapping keyGenerator="KeyGenerator.GUIDGen" primaryTable="ActivityPlanStepSignatory">          <AttributeMappings>             <AttributeMapping destinationKey="UserPerson.PK" name="entity" sourceKey="APStepSignatory.PK.FK_UPrsn"/>             <AttributeMapping destinationKey="ActivityPlanStep.PK" name="step" sourceKey="APStepSignatory.PK.FK_Step"/>          </AttributeMappings>       </RelationalMapping>    </PersistenceMapping> </Class>

 

0

[Nicholas Mc Neilly]

We are currently looking into this item a bit more and will provide an update by tomorrow.

0

[Nicholas Mc Neilly]

Upon further review. We believe the issue reported is a new defect. A ticket has been created in our system to track this issue. It is currently targeted to our December 2021 release.

0

• This reply was modified 3 years, 2 months ago by Nicholas Mc Neilly.

[Author]

Posts