<< Click to Display Table of Contents >>
Navigation: Bizagi Work Portal > Me >
My Stuff holds all the data that each Stakeholder owns and is relevant to their work.
This data is available for each Stakeholder independently, and displays all records that are allocated, or owned by that logged-in Stakeholder.
This section is part of the personalized Me menu, which is described at Me.
My Stuff's presentation
Within My Stuff, many different collection of data is presented.
Each collection of My Stuff represents a collection linked to that Stakeholder.
The sample image below shows how a Patient Stakeholder is be able to see his/her exams, his/her medical bills, among others, because those are data records that belong to that particular user.
Bear in mind that My Stuff is also context-aware; which means that some collections may be shown to that Stakeholder under a particular situation or circumstance instead of being always shown.
Using My stuff
When clicking on a collection, you will be displayed with the values stored in that collection that are exclusively associated to the current Stakeholder.
Once a collection is clicked, the data records in them will be presented with these options:
Note that the information is presented using the preset Template of the specific entity which holds records.
To learn more on how this is configured in Bizagi Studio, refer to Entity Templates.
Whenever the template is bound to the process entity, the Work on it button will be available (provided that the case is opened and there is an activity allocated to the user).
Notice you can filter results by using the options located on top of the listed records.
In that header, you may use more than one filter at the same time:
The number of filters applied to the results will be represented with the funnel icon and a number on it (), located at the top right corner.
When clicked on, you may toggled on/off such filters.
The values available for filtering are those that are contained within the list of results. For example, if within the results there are records associated with English and Spanish languages, the filter will show these available values. This is so, even if the source entity contains more values such as English, Spanish, Portuguese, Italian.
•When performing Searches, the filters used will be automatically removed to avoid performance inconveniences when results surpass 1,000 records.
•Indirect collections will not display the Filters nor the Order by options in the Work Portal. For these relations, filters are defined at design time but are not displayed to be managed at run-time.
Similarly, results can be sorted out by using the attributes presented for each result.
Sort these records in ascendant or descendant order, depending on the direction the arrow of the () icon points to.
For instance, this specific example (the icon shown above) works for an ascending order.
My Stuff shortcuts
Note that while viewing a given collection of My Stuff, the panel on the left will present a shortcut for you to access any other collection of My Stuff.
Knowledge workers are able to add new records to their existing collections, for those collections this possibility is explicitly enabled.
When enabled, the collection will display an "Add.." option at the top of the listed records.
Clicking it, will open a form to input details, or launch a process.
The choice of having a form or a process be launched, as well as the possibility to use this option (it being enabled) are defined in design through Bizagi Studio.
To learn more on how this is configured in Bizagi Studio, refer to Enabling new items in My Stuff.
Executing Actions over records
Each record may display buttons, that are active according to a given situation (context).
These buttons represent Actions.
Important aspects of such Actions are:
•They enable Stakeholders to achieve an objective that he/she consciously wills.
•They can launch processes, update data records with the click of a button (independent of the processes it is related to), create new records of an entity (also being independent of a process), and link process together to create powerful cases.
•They can be launched to affect or create an individual data records of your project, or multiple records at the same time.
For example, an Action can end up booking a hotel, updating a customer's record, or approve multiple requests at the same time.
Individual actions vs batch actions
Actions that affect individual records are shown on the bottom of each record.
Hence, notice that a record may present different Actions when compared to other ones (Bizagi will display Actions when it makes sense given a particular situation).
The image below illustrates an example where a Stakeholder is viewing his/her doctors, and how that stakeholder does not have the possibility to schedule an appointment with Doctor Adam Smith because that doctor is a Pathologist, unlike with Doctor Alexandre Mou, who is a General practitioner.
On the other hand, whenever an Action is presented at the top of the listed records, it means that it may be clicked once to make it apply to multiple records (as long as you tick the check boxes of the records it should apply to).
These type of Actions are known as Batch Actions.
Notice that while ticking check boxes of different records, Bizagi will present those Batch Actions which are applicable to the whole set of the records (under a "their common denominator" approach).
To learn more about how are Actions configured in Bizagi Studio, refer to Actions.