Home › Forums › implementation › Implementation discussion ›

act.reasonName

Submitted by dadmin on Fri, 25/04/2014 - 22:55
in

Why do act.reasonName and act.reason in a worklist or schedule return blank?

Matt Y.

 

‹ Getting access to line item tax type Are the default mysql user values currently installed in the distribution the smartest ones? ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: act.reasonName

Submitted by tanderson on Sat, 26/04/2014 - 01:20.

These two are only set for appointments. How are you trying to use them? It should be something like:

openvpms:get(.,'act.reasonName')

or:

openvpms:get(.,'act.reason')

They both come from the 'reason' node of act.customerAppointment; this contains the code of a lookup.appointmentReason. The act.reasonName is just a shortcut for:

openvpms:lookup(., 'reason')

Re: [OpenVPMS] act.reasonName

Submitted by dadmin on Sat, 26/04/2014 - 23:03.



Tim,


I'm using them in the expression for a worklist view.

Matt.





Re: [OpenVPMS] act.reasonName

Submitted by tanderson on Sat, 26/04/2014 - 23:16.

Work lists events are derived from the act.customerTask archetype. This doesn't have a reason node, so the act.reasonName and act.reason properties will always be empty.

Re: act.reasonName

Submitted by tgething (not verified) on Sat, 26/04/2014 - 08:27.

Matt - I just checked the CSH text at http://www.openvpms.org/documentation/csh/1.7/admin/organisation/worklis... - it does say:

(actually it now says '...which can be used' after I noticed and corrected the grammatical error)

whereas the appointment equivalent at http://www.openvpms.org/documentation/csh/1.7/admin/organisation/schedul... says:

so at least the behaviour is documented correctly - and the 'blank for tasks' simply reflects the fact that there is no reason field in the act.customerTask archetype.

Regards, Tim G

Syndicate content