Hi We are currently working on an implementation of some process support. We are in general using archetypes for our modelling and we have found Instruction/Action to be well suited for our current need. Actions will tell the current state of each activity and based on this state new steps will be available. We intend to present this to our user so that only the steps currently available will be presented in the user interface. This can be inferred by our software from the generic ISM and the particular careflow steps modelled in the actual Action.
In setting this up we have come across a severe limitation in the tools we use for modelling. Neither the Archetype Editor (AE) nor the Template Designer (TD) supports the transition property of the ISM_Transition class. Without this information we are not able to infer legal actions from the current state; how can you distinguish "resume" from "active_step" when all you know is their current_state (i.e. end state), which in this case is the same? When the current state is SUSPENDED we certainly only want to present to the user "resume", but with this limitation we are forced to present all transitions that has ACTIVE as its current_state. This introduces both hazards and poor usability. We have tried to edit the ADL-file in a text editor, adding the missing information. When opening and saving the file from AE this will again disappear and the OPT generated by TD has no trace of the transition information, so they both seem to be completely ignorant of this essential piece of information. Are there any plans to include transition support in these tools? Is there anything we are overlooking in our approach? Vennlig hilsen Ivar Yrke Senior systemutvikler Telefon +47 75 59 24 06 Mobil +47 90 78 89 33 www.dips.no<http://www.dips.no> [cid:[email protected]] Denne meldingen er bare ment for mottakeren, og kan inneholde fortrolige opplysninger eller annen privat informasjon. Hvis du mottar denne ved en feil, vær så vennlig å varsle avsender og slett meldingen.
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
