Note that records belonging to these sets may show up in more that one collection, and that there is an important notion regarding temporarily useful information with indirect collections, in which you will need to make sure you have attributes (i.e Boolean) to filter if patients are critical or non-critical, and currently under care or no longer under care. For example, using different filters to display separately: the complete list of patients I am attending, the list of critical patients I am attending, and the list of non-critical patients I am attending. Allows design-time filters, so that you can display multiple sets while being linked to the same collection.Powerful features supported by indirect collections are: The difference when compared to a direct collection is that indirect collections are a new concept within Experience design, that leverages the use of My stuff section because these are especially designed to feature quick/easy access to relevant data which a stakeholder needs for follow-up tasks.įor example, a Doctor or Nurse stakeholder may rely on indirect collections to easily access the list of patients currently under his/her care. Instead, these are more focused on providing a shortcut for the stakeholder to access certain information which is relevant for him/her at the time (i.e, this means that such collection could hold information which is only useful temporarily). Indirect collections are XPath definitions, which also support one-to-many navigation but without necessarily implying the concept of "ownership" between the 2 entities involved. Though you may create new direct collections in this section, recall that you may also create them by editing the stakeholder entity (when defining or modifying the stakeholder) in the Experience design, or at the Process view or Expert view, just as part of steps involved in the design of your data model. In terms of stakeholders and while using a Doctor as an example stakeholder, it would mean that he/she would have a direct collection of appointments: Usually when there is an ownership concept involved (e.g a Customer has many registered phone numbers), then a direct collection is appropriate. If you were familiar with previous versions, then nothing has changed regarding such collections, and these are both still useful and especially required from the processes' perspective (e.g, to display tables with rows of information inside of activity forms). Such type of collections belong to the traditional Bizagi way in which these were created in previous versions and are always visible at the Entity's data model diagram: All the patients which are currently under his/her care.īefore getting into detail about My stuff configuration, consider that collections in Bizagi are now classified into 2 different types: Direct collections and Indirect collections.ĭirect collections are one-to-many relationships which are created explicitly in the data model.The working shifts which are scheduled for that nurse.
While referring to the example on how a Hospital's Emergency Room operates, and parting from having a Nurse stakeholder, we may configure as part of My stuff: My stuff is designed as a section in the Work portal that presents in one place, all sets of information which are of interest to a stakeholder.Īnd because Bizagi is context-aware, you could have different sets show up according to the context on which the stakeholder is in. Such data sets are depicted for the user experience as collections that are part of My stuff. Once you have initially depicted the different contexts for your stakeholders, as described at Contexts, you will now be able to sort out the things that apply to a stakeholder while specifically found under a given context.ĭefining data sets that belong to (or are bound to) that stakeholder, are among these things you classify per context.
0 kommentar(er)
