more english translations + pictures added + completion of certain parts
45
user/English/activity.md
Normal file
@ -0,0 +1,45 @@
|
|||||||
|
\newpage
|
||||||
|
|
||||||
|
# Activities (exchanges)
|
||||||
|
<!-- en/activity/?accompanying_period_id={id} -->
|
||||||
|
|
||||||
|
![List of exchanges related to a course](screenshot/img/en_activity__accompanying_period_id_2705.png)
|
||||||
|
|
||||||
|
Activities (or exchanges) in Chill are used to record activities or exchanges that have taken place and to link them to users and/or support pathways. By activity, we mean an individual interview, an approach via an external
|
||||||
|
partner, a telephone call relating to the person, an e-mail, etc.
|
||||||
|
|
||||||
|
The information to be encoded is different according to the type of activity.
|
||||||
|
For example, for a telephone call, you can specify the duration of the call, the caller and take a note. For a meeting, you can associate a location (the place where the meeting took place), the parties present at the meeting, notes, documents, etc.
|
||||||
|
|
||||||
|
In this way, this information can be centralised and then easily shared between the social workers.
|
||||||
|
|
||||||
|
The types of activities and their corresponding fields (location, duration, travel time, documents, presence of the person, users, etc.) can be configured in the administration area.
|
||||||
|
|
||||||
|
|
||||||
|
## Activity in persons or trajectories?
|
||||||
|
|
||||||
|
The activities can be encoded in the person or in the support path. It is up to you to choose whether to encode activities in the context of a support pathway or in the context of a person. However, as soon as a person is mentioned in an activity, this activity can be found in the list of activities of the person.
|
||||||
|
|
||||||
|
Example: In the support path of the user Gabrielle Durant, I create an activity concerning an email where I also mention another user encoded in Chill: Dominique Duchemin. The activity will be visible in Gabrielle Durant's support path, but also in her user file and in Dominique Duchemin's file.
|
||||||
|
|
||||||
|
We can therefore access the list of activities of a person via the "user" menu and the list of activities of a support path via the "support path" menu.
|
||||||
|
|
||||||
|
## Create and modify an activity
|
||||||
|
|
||||||
|
In the list of activities, click on the "Create" button to create a new activity. First choose the type of activity/exchange, then fill in the relevant information. If the activity has been created in a pathway, the social issues and related support actions will be filled in. Depending on the type of activity, you will be able to fill in the parties involved, the date, the location, the duration of the activity, the possible travel time (in case of a trip), documents, the subject, a free note, etc.
|
||||||
|
|
||||||
|
The subject is taken from a predefined list, established in the administration area of the software.
|
||||||
|
|
||||||
|
Any type of document can be added to an activity: a text document, a pdf, a photo, etc.
|
||||||
|
|
||||||
|
The parties involved, users, third parties or users (social worker), are added by searching for people already encoded in Chill or by creating them on the fly. If the activity has been created in a pathway, you can easily add parties involved by clicking on the proposed names. The proposals are based on the parts mentioned in the accompanying course.
|
||||||
|
|
||||||
|
::: { .info }
|
||||||
|
|
||||||
|
It is possible to transform an appointment into an activity. (TODO)
|
||||||
|
|
||||||
|
:::
|
||||||
|
|
||||||
|
Once an activity has been created, it is always possible to modify it to make corrections or additions.
|
||||||
|
|
||||||
|
## Effects of the selection of issues or actions on trajectories
|
@ -12,11 +12,12 @@ A side activity could be a team meeting, a training, but also a phone call or em
|
|||||||
|
|
||||||
A user can navigate to his/her list of side activities from within their user menu by clicking on <**My side activities**>. Similar to other sections of the Chill app, you will find here a list that offers a first quick overview of each activity. You can view the activity in more detail, edit, or delete it.
|
A user can navigate to his/her list of side activities from within their user menu by clicking on <**My side activities**>. Similar to other sections of the Chill app, you will find here a list that offers a first quick overview of each activity. You can view the activity in more detail, edit, or delete it.
|
||||||
|
|
||||||
|
|
||||||
## Creating a side activity
|
## Creating a side activity
|
||||||
|
|
||||||
<!-- /fr/asideactivity/new -->
|
<!-- /fr/asideactivity/new -->
|
||||||
|
|
||||||
|
![Creation aside activity](/user/img/new_aside_activity.png)
|
||||||
|
|
||||||
The form fields of a side activity are self-explanatory. It is important to note however that a user can create a side activity for another user. Multiple users can also be linked, think of a meeting for example.
|
The form fields of a side activity are self-explanatory. It is important to note however that a user can create a side activity for another user. Multiple users can also be linked, think of a meeting for example.
|
||||||
|
|
||||||
A side activity can be created for the future, but they can also still be created for activities that already took place. As such it shouldn't be seen as a planning tool, but more to keep record of side activities.
|
A side activity can be created for the future, but they can also still be created for activities that already took place. As such it shouldn't be seen as a planning tool, but more to keep record of side activities.
|
||||||
|
91
user/English/household.md
Normal file
@ -0,0 +1,91 @@
|
|||||||
|
/newpage
|
||||||
|
|
||||||
|
# Households {#sec:household}
|
||||||
|
|
||||||
|
## What is a household?
|
||||||
|
|
||||||
|
A household is a set of users living 'under the same roof'. This can be members of a family, members of a blended family, members of a foster family, etc.
|
||||||
|
<!-- Living "under the same roof" OR living at the same address? -->
|
||||||
|
|
||||||
|
A household is characterised by an address, which corresponds to the home address of its members. This address can change (in case of a move): it is therefore defined between a start date and an end date and there may be a history of household addresses. Similarly, a user may change household and have a history of households.
|
||||||
|
|
||||||
|
## Household summary
|
||||||
|
|
||||||
|
<!-- /en/person/household/{household_id}/summary -->
|
||||||
|
|
||||||
|
![Household Summary](screenshot/img/en_person_household_376_summary.png)
|
||||||
|
|
||||||
|
The household summary page is accessed via the "person" menu or by clicking on the household icon in the person search. The household summary page shows the current household address, the household members and the composition of the household.
|
||||||
|
|
||||||
|
The household address history can be accessed in the household menu under the heading "Address history". The address history shows all successive household addresses and allows for additions.
|
||||||
|
|
||||||
|
<!-- /en/person/household/{household_id}/addresses -->
|
||||||
|
|
||||||
|
![Household address history](screenshot/img/en_person_household_376_addresses.png)
|
||||||
|
|
||||||
|
A list of the household's trajectories can also be displayed by clicking in the household menu on <**trajectories**>.
|
||||||
|
|
||||||
|
|
||||||
|
### Create a household
|
||||||
|
|
||||||
|
If there is no household in the list of households for a user, then the software allows you to create a new household. At this stage, you can create a new household or join an existing one. The software will automatically propose possible households by making some suggestions.
|
||||||
|
|
||||||
|
#### Which households are suggested?
|
||||||
|
|
||||||
|
The software tries to establish links between the persons concerned by the change of household, and other households.
|
||||||
|
|
||||||
|
The links made are as follows:
|
||||||
|
|
||||||
|
* For each person affected by the change, the software checks whether he or she is present in another support trajectory, with other persons. If these persons are themselves associated with a household, then the software proposes to join that existing household.
|
||||||
|
* The software also examines the location of the support trajectories in which the person, concerned by the change, is located. If a support trajectory is located at a reference address, the software looks to see if there are other households living at that address. If it finds any, these households will also be suggested.
|
||||||
|
|
||||||
|
At this stage, you can enter an address; this will immediately locate the created household. The software will suggest you to re-use known addresses.
|
||||||
|
|
||||||
|
#### Which addresses are suggested?
|
||||||
|
|
||||||
|
The software suggests you to re-use the temporary location of the support trajectories associated with the household members.
|
||||||
|
|
||||||
|
For each person who is going to "change household", the software examines whether he is currently associated with a trajectory. If this trajectory has a temporary address, then this address will be included in the suggestions.
|
||||||
|
|
||||||
|
|
||||||
|
### Positions in the household
|
||||||
|
|
||||||
|
<!-- note that the positions "children outside the household", etc., are configurations -->
|
||||||
|
|
||||||
|
Each member of the household is detailed in the "household summary" page. The person can have a certain position in the household: adult or child, as well as being the owner of a household. At any time it is possible to remove a person from a household, or to reposition him/her in the household (e.g. to make him/her the owner).
|
||||||
|
|
||||||
|
If necessary, it is also possible to view a former membership, i.e. a person who used to belong to the household but is no longer part of it.
|
||||||
|
|
||||||
|
|
||||||
|
## Add members to the household, leave a household, join a household
|
||||||
|
|
||||||
|
At the bottom of the household summary page, the <**Add a member**> button allows you to add a user to the household. When clicking on this button, in the following pages, one can:
|
||||||
|
|
||||||
|
- add one or more existing persons, or create new ones;
|
||||||
|
- position each person in the household, i.e. specify whether he/she is a child or an adult, and possibly qualify him/her as a household member;
|
||||||
|
- enter the date when the person joins the household, and possibly a comment;
|
||||||
|
- and, finally, save.
|
||||||
|
|
||||||
|
In the list of household members, using the buttons on the right, one can
|
||||||
|
|
||||||
|
- leave the household: in this case, the person can join another household or leave without joining a household. Again, a change date is encoded.
|
||||||
|
- reposition the member: i.e. change the position (adult, child, ...) of the member.
|
||||||
|
- fill in the membership: i.e. change the date and the comment of the change
|
||||||
|
|
||||||
|
|
||||||
|
## Affiliations
|
||||||
|
<!-- /en/person/household/{household_id}/relationship -->
|
||||||
|
|
||||||
|
![Affiliations of a houshold](user/img/menage_filiations.png)
|
||||||
|
|
||||||
|
The "affiliations" page provides an overview in graph form of the affiliations within a household, i.e. the relationships between its members. This page allows not only to view the relationships but also to edit them. By clicking on <**Create a relationship**>, then selecting 2 persons, it is possible to define the relationship between these 2 persons: mother/father-daughter/son, brother/sister-brother/sister, uncle/aunt-nephew/niece.
|
||||||
|
|
||||||
|
In addition, the graph also shows the support trajectories associated with each household member. By displaying the trajectory, persons who may be linked to these trajectories, but belong to other households can be displayed. The elements of the graph can be moved by clicking and dragging. Finally, the graph can be exported as an image.
|
||||||
|
|
||||||
|
In short, this page summarises a household and its relationships in an easy-to-understand diagram.
|
||||||
|
|
||||||
|
## Family composition
|
||||||
|
|
||||||
|
The family composition is a qualification of the household as a household type, e.g. couple with children, couple without children, single mother, single woman, etc. This composition is valid until a certain date and with a maximum of one year.
|
||||||
|
|
||||||
|
As with the addresses of a household, it is possible to view the history of the composition of a household.
|
9
user/English/metadata.yaml
Normal file
@ -0,0 +1,9 @@
|
|||||||
|
---
|
||||||
|
title: Chill user manual
|
||||||
|
lang: en-EN
|
||||||
|
toc: true
|
||||||
|
|
||||||
|
|
||||||
|
header-includes: |
|
||||||
|
\usepackage{awesomebox}
|
||||||
|
...
|
36
user/English/notifications.md
Normal file
@ -0,0 +1,36 @@
|
|||||||
|
\newpage
|
||||||
|
|
||||||
|
# Notifications
|
||||||
|
<!-- en/notification/inbox -->
|
||||||
|
|
||||||
|
![Notification inbox](screenshot/img/en_notification_inbox.png)
|
||||||
|
|
||||||
|
Notifications are messages sent by one user to one or more others. The purpose of notifications is to quickly exchange information about ongoing social cases between social workers. For example, notifications can be used to inform a caseworker about a case.
|
||||||
|
|
||||||
|
They can be accessed either from the Chill homepage, under the "My notifications" tab, or anywhere in the application via the "user" menu at the top right of the screen. Depending on the configuration chosen by the software administrators, notifications are also sent by email to the social worker concerned.
|
||||||
|
|
||||||
|
## Create a notification
|
||||||
|
<!-- en/notification/create?entityClass=Chill%5CPersonBundle%5CEntity%5CAccompanyingPeriod&entityId=2705-->
|
||||||
|
|
||||||
|
![Create a notification](user/img/notification_parcours.png)
|
||||||
|
|
||||||
|
Notifications can be sent from several places in the software. A notification consists of a subject (such as an email), one or more recipients, a message and the information from which the notification is sent. For example, when sending a notification as part of a course, the general course information is also copied.
|
||||||
|
|
||||||
|
It is possible to send a notification:
|
||||||
|
|
||||||
|
- from the summary page of a support trajectory
|
||||||
|
- from an activity/exchange
|
||||||
|
|
||||||
|
Notifications sent, for example, from a support trajectory, are listed in the trajectory summary.
|
||||||
|
|
||||||
|
<TODO: Are there any other places where notifications are used? -->
|
||||||
|
|
||||||
|
In addition, there are notifications that are automatically sent when certain actions are taken.
|
||||||
|
|
||||||
|
|
||||||
|
## Discuss in a notification
|
||||||
|
<!-- en/notification/{notification_id}/show -->
|
||||||
|
|
||||||
|
![Discussion in a notification](screenshot/img/en_notification_126_show.png)
|
||||||
|
|
||||||
|
When a notification is received, it is possible to start a discussion with the recipient in the notification page. This allows messages to be left between workers, as in an online chat system.
|
98
user/English/person.md
Normal file
@ -0,0 +1,98 @@
|
|||||||
|
\newpage
|
||||||
|
|
||||||
|
# Person file {#sec:person}
|
||||||
|
|
||||||
|
The person file contains all the information specific to the person: surname, first name, contact information, addresses, etc. It is the basis of the person's electronic social file.
|
||||||
|
|
||||||
|
It can be accessed by searching for a person on the homepage or in the toolbar. It can also be accessed from other pages by clicking on a person's name and then clicking on "Open person file".
|
||||||
|
|
||||||
|
<!-- TODO a déplacer vers une autre section, sur le concept de l'usager? -->
|
||||||
|
A person can be part of one or more households. For each person, it is possible to define support trajectories. Finally, each person is linked to exchanges in which the person is involved.
|
||||||
|
|
||||||
|
## Create a person
|
||||||
|
<!-- fr/person/new -->
|
||||||
|
|
||||||
|
![Create a person](screenshot/img/fr_person_new.png)
|
||||||
|
|
||||||
|
To add a person, click on "Sections" > "Add a person", in the top toolbar.
|
||||||
|
|
||||||
|
In the creation page, enter the requested information. Only the surname, first name(s) and gender are mandatory. Then click on "Create person". You can then choose between simply creating the person, creating the person and associating him/her with a household or creating the person and creating an associated support trajectory.
|
||||||
|
|
||||||
|
::: { .info }
|
||||||
|
|
||||||
|
Please note that there is a standard format for entering telephone numbers. Enter your numbers without spaces, "/" bars or "-" dashes.
|
||||||
|
<!-- TODO d'autres contraintes sur les numéros de tel? -->
|
||||||
|
:::
|
||||||
|
|
||||||
|
## Person detail page
|
||||||
|
<!-- fr/person/{id}/general -->
|
||||||
|
|
||||||
|
![Person detail page](screenshot/img/fr_person_2811_general.png)
|
||||||
|
|
||||||
|
The person record contains all the detailed information of the person, namely:
|
||||||
|
|
||||||
|
- surname, first name(s), gender;
|
||||||
|
- nationality, languages spoken, number of children, marital status
|
||||||
|
- date and place of birth;
|
||||||
|
- contact information.
|
||||||
|
|
||||||
|
This information can be filled in as you go along, or left blank. At the bottom of the page, the "Edit" button allows you to edit this information. Remarks can also be added.
|
||||||
|
|
||||||
|
Some of this information is recalled in the person's banner and in other places in the software when the person's name is clicked on.
|
||||||
|
|
||||||
|
## Person addresses
|
||||||
|
|
||||||
|
Chill supports two types of addresses:
|
||||||
|
|
||||||
|
* home addresses, which are the permanent, official addresses of a person (home address);
|
||||||
|
* residence addresses, which are temporary addresses of a person, at which he/she resides only for a certain period of time, and which is not intended to be official.
|
||||||
|
|
||||||
|
Therefore, the official address is not attached directly to a person, but to his or her household. Only residential addresses can be entered in the person's file.
|
||||||
|
|
||||||
|
## Home address
|
||||||
|
<!-- /fr/person/{id}/residential-address/list -->
|
||||||
|
|
||||||
|
![Person home address](screenshot/img/fr_person_2811_residential-address_list.png)
|
||||||
|
|
||||||
|
Each person can have one or more home addresses. These are accessed by clicking on "Home addresses" in the right-hand menu.
|
||||||
|
|
||||||
|
These addresses are not supposed to be official home addresses, declared to the authorities. They are, for example, a temporary residence in a nursing home, accommodation with an acquaintance or friend for a specific period of time, etc.
|
||||||
|
|
||||||
|
When adding a residence address, there is a choice between
|
||||||
|
|
||||||
|
- taking an address from another person (from another person);
|
||||||
|
- taking an address from a third party;
|
||||||
|
- create a new address [address](#sec:choose-an-address).
|
||||||
|
|
||||||
|
## Resource persons
|
||||||
|
<!-- /fr/person/{id}/resources/list -->
|
||||||
|
|
||||||
|
![resource persons](screenshot/img/fr_person_2811_resources_list.png)
|
||||||
|
|
||||||
|
Resource persons are other persons or third parties associated with the person's file. A contact person may be a friend or neighbour (another person), a health professional (a third party), etc. Other members of the person's household should be entered in the "household" section instead. If the contact person is not encoded, he/she can also be added as a free description.
|
||||||
|
|
||||||
|
|
||||||
|
<!-- ## Historique
|
||||||
|
<!-- /fr/person/{id}/timeline
|
||||||
|
|
||||||
|
TODO -->
|
||||||
|
|
||||||
|
## Treating doubles
|
||||||
|
<!-- /fr/person/{id}/duplicate/view -->
|
||||||
|
|
||||||
|
It is possible that a person has been encoded more than once. The "Dealing with duplicates" page allows you to identify and deal with possible duplicates of a person. The page lists persons with similar names and suggests merging them.
|
||||||
|
|
||||||
|
::: { .info }
|
||||||
|
|
||||||
|
This page is used to process duplicates, but Chill also automatically detects potential duplicates when encoding a new person.
|
||||||
|
|
||||||
|
:::
|
||||||
|
## Other person menu entries
|
||||||
|
|
||||||
|
There are several entries in the person menu that link to other parts of the software, keeping the link to the person. These entries are:
|
||||||
|
|
||||||
|
* Support trajectories: list of the trajectories in which the person is involved;
|
||||||
|
* Activities (or exchanges): list of activities in which the person is involved;
|
||||||
|
* Documents: list of documents in which the person is involved;
|
||||||
|
* Tasks: list of tasks in which the person is involved;
|
||||||
|
* Households: management of the person's household.
|
@ -11,6 +11,8 @@ __note__: Social actions can only be created for **confirmed** trajectories.
|
|||||||
|
|
||||||
<!-- /fr/person/accompanying-period/{id}/work -->
|
<!-- /fr/person/accompanying-period/{id}/work -->
|
||||||
|
|
||||||
|
![social_action](/user/img/action_accompagnement.png)
|
||||||
|
|
||||||
Similar to many other sections within the Chill application, a list of social support actions can be found by clicking on <**social support actions**> in the yellow side-menu of a trajectory.
|
Similar to many other sections within the Chill application, a list of social support actions can be found by clicking on <**social support actions**> in the yellow side-menu of a trajectory.
|
||||||
|
|
||||||
A concise overview of important information is given for each action in the list.
|
A concise overview of important information is given for each action in the list.
|
||||||
@ -62,9 +64,10 @@ Concerned persons within the trajectory are listed here and the user can select
|
|||||||
|
|
||||||
### Treating thirdparties
|
### Treating thirdparties
|
||||||
|
|
||||||
TODO: what is the difference between these two?
|
If an external partner executed the social action, they can be identified here.
|
||||||
|
Think of them as the main actor.
|
||||||
|
|
||||||
### Intervening thirdparties
|
### Intervening thirdparties
|
||||||
|
|
||||||
|
These are external partners that participate(d) in the social action, but are not the main actors.
|
||||||
|
|
||||||
|
@ -6,6 +6,18 @@ Providing meaningful social support is often an intricate combination of goals,
|
|||||||
|
|
||||||
You can look at it as the third big module within the application. Like the person and household modules it can be easily identified by the banner at the top of the screen, which is in this case **gray** in color.
|
You can look at it as the third big module within the application. Like the person and household modules it can be easily identified by the banner at the top of the screen, which is in this case **gray** in color.
|
||||||
|
|
||||||
|
![Trajectory banner](/user/img/banner_course.png)
|
||||||
|
|
||||||
|
## Trajectory overview
|
||||||
|
|
||||||
|
![Trajectory dashboard](/user/img/parcours_dashboard.png)
|
||||||
|
|
||||||
|
<!-- /fr/parcours/{id} -->
|
||||||
|
|
||||||
|
The overview page assembles the most important information and latest activity within a trajectory, allowing you to take certain quick actions like clicking on associated person badges, linked activities or social actions, sending a new notification, etc...
|
||||||
|
|
||||||
|
In short it is the trajectory dashboard from where you will navigate to specific sections.
|
||||||
|
|
||||||
## Creation of a social support trajectory
|
## Creation of a social support trajectory
|
||||||
|
|
||||||
<!-- /fr/parcours/{id}/edit -->
|
<!-- /fr/parcours/{id}/edit -->
|
||||||
@ -46,14 +58,20 @@ The information required to **confirm** a trajectory is the following:
|
|||||||
* It is assigned to at least one [service](#service).
|
* It is assigned to at least one [service](#service).
|
||||||
* It has to be [localised](#trajectory-localisation).
|
* It has to be [localised](#trajectory-localisation).
|
||||||
|
|
||||||
|
![Confirm trajectory](/user/img/parcours_confirm.png)
|
||||||
|
|
||||||
All of these requirements are listed at the bottom of the form when you have failed to fulfill them. This serves as a reminder to what you should do in order to confirm the trajectory.
|
All of these requirements are listed at the bottom of the form when you have failed to fulfill them. This serves as a reminder to what you should do in order to confirm the trajectory.
|
||||||
|
|
||||||
### Concerned person
|
### Concerned person
|
||||||
|
|
||||||
|
![Concerned persons](/user/img/concerned_persons.png)
|
||||||
|
|
||||||
A trajectory can be put started to provide support to multiple persons (eg. support is given to a mother and her two children).
|
A trajectory can be put started to provide support to multiple persons (eg. support is given to a mother and her two children).
|
||||||
|
|
||||||
### Trajectory localisation
|
### Trajectory localisation
|
||||||
|
|
||||||
|
![Localisation](/user/img/parcours_localisation.png)
|
||||||
|
|
||||||
Every trajectory **has** to be localised and this can be done in one of two ways.
|
Every trajectory **has** to be localised and this can be done in one of two ways.
|
||||||
|
|
||||||
1. You can indicate a temporary address by clicking the designated button. The address will not automatically be adapted when a concerned person moves. Therefore a message is displayed to remind you as a user that the second option, here listed, is preferable.
|
1. You can indicate a temporary address by clicking the designated button. The address will not automatically be adapted when a concerned person moves. Therefore a message is displayed to remind you as a user that the second option, here listed, is preferable.
|
||||||
@ -84,7 +102,7 @@ TODO
|
|||||||
|
|
||||||
### The applicant
|
### The applicant
|
||||||
|
|
||||||
This can be an already existing person/thirdparty or a new applicant can be created from within the search modal. Click on the button **<create 'your-search-name'>** to do so.
|
This can be an already existing person/thirdparty or a new applicant can be created from within the search modal. Click on the button <**create 'your-search-name'**> to do so.
|
||||||
|
|
||||||
### Social issue
|
### Social issue
|
||||||
|
|
||||||
@ -109,14 +127,6 @@ Likewise a referrer cannot be removed from a confidential trajectory.
|
|||||||
A trajectory is setup to provide support to one or more concerned persons. Naturally, there may also be one or more thirdparties or persons involved to offer this support. These partners can be added in this section by searching for their name.
|
A trajectory is setup to provide support to one or more concerned persons. Naturally, there may also be one or more thirdparties or persons involved to offer this support. These partners can be added in this section by searching for their name.
|
||||||
When a partner does not yet exist they can be created from within the search modal by pressing the button **<create 'your-search-name'>**.
|
When a partner does not yet exist they can be created from within the search modal by pressing the button **<create 'your-search-name'>**.
|
||||||
|
|
||||||
## Trajectory overview
|
|
||||||
|
|
||||||
<!-- /fr/parcours/{id} -->
|
|
||||||
|
|
||||||
The overview page assembles the most important information and latest activity within a trajectory, allowing you to take certain quick actions like clicking on associated person badges, linked activities or social actions, sending a new notification, etc...
|
|
||||||
|
|
||||||
In short it is the trajectory dashboard from where you will navigate to specific sections.
|
|
||||||
|
|
||||||
## Trajectory history
|
## Trajectory history
|
||||||
|
|
||||||
<!-- /fr/parcours/{id}/history -->
|
<!-- /fr/parcours/{id}/history -->
|
||||||
|
@ -28,6 +28,8 @@ A separate user menu entry will take you directly to a listing page of all your
|
|||||||
|
|
||||||
<!-- /fr/task/single-task/new -->
|
<!-- /fr/task/single-task/new -->
|
||||||
|
|
||||||
|
![Creation task](/user/img/new_task.png)
|
||||||
|
|
||||||
To create a new task you will be given a form to fill in.
|
To create a new task you will be given a form to fill in.
|
||||||
The fields are self-explanatory but do note that only the title is required.
|
The fields are self-explanatory but do note that only the title is required.
|
||||||
|
|
||||||
|
@ -23,6 +23,8 @@ These are most likely individual professionals working within the organization o
|
|||||||
|
|
||||||
### Legal entity
|
### Legal entity
|
||||||
|
|
||||||
|
![Legal entity](/user/img/thirdparty_morale.png)
|
||||||
|
|
||||||
Creating a **legal entity** takes you to a form which you can complete with the following information.
|
Creating a **legal entity** takes you to a form which you can complete with the following information.
|
||||||
|
|
||||||
* **Name**
|
* **Name**
|
||||||
@ -37,14 +39,16 @@ Creating a **legal entity** takes you to a form which you can complete with the
|
|||||||
|
|
||||||
* **Contacts**: Contacts are natural persons associated with the legal entity. You can specify their title and role within the entity and add their contact information. As with the address above there is an option to make it a confidential contact. Their information will thus be blurred throughout the application and can be revealed when needed. Each contact can be deleted individually and these changes will be saved when saving the entire entity.
|
* **Contacts**: Contacts are natural persons associated with the legal entity. You can specify their title and role within the entity and add their contact information. As with the address above there is an option to make it a confidential contact. Their information will thus be blurred throughout the application and can be revealed when needed. Each contact can be deleted individually and these changes will be saved when saving the entire entity.
|
||||||
|
|
||||||
|
![Thirdparty contact](/user/img/thirdparty_contact.png)
|
||||||
|
|
||||||
* **Comment**
|
* **Comment**
|
||||||
* **Active/inactive**: a thirdparty can be set to inactive (eg. they are no longer operational).
|
* **Active/inactive**: a thirdparty can be set to inactive (eg. they are no longer operational).
|
||||||
|
|
||||||
---------
|
---------
|
||||||
|
|
||||||
### Natural person
|
### Natural person
|
||||||
|
|
||||||
A natural person is a thirdparty that is not linked to a larger entity within the CHILL application. Within the form the following can be specified,
|
A natural person is a thirdparty that stands on it's own. Although a thirdparty contact is in fact also a natural person, they are two distinct entities in Chill.
|
||||||
|
Within the form the following can be specified,
|
||||||
|
|
||||||
* **Civil title** (eg. Mrs., Mayor, ...)
|
* **Civil title** (eg. Mrs., Mayor, ...)
|
||||||
* **Name**
|
* **Name**
|
||||||
|
Before Width: | Height: | Size: 35 KiB |
Before Width: | Height: | Size: 610 B |
Before Width: | Height: | Size: 39 KiB |
Before Width: | Height: | Size: 7.8 KiB |
Before Width: | Height: | Size: 35 KiB |
Before Width: | Height: | Size: 54 KiB |
Before Width: | Height: | Size: 44 KiB |
Before Width: | Height: | Size: 72 KiB |
BIN
user/img/action_accompagnement.png
Normal file
After Width: | Height: | Size: 67 KiB |
Before Width: | Height: | Size: 44 KiB After Width: | Height: | Size: 44 KiB |
Before Width: | Height: | Size: 58 KiB After Width: | Height: | Size: 58 KiB |
Before Width: | Height: | Size: 43 KiB After Width: | Height: | Size: 43 KiB |
Before Width: | Height: | Size: 46 KiB After Width: | Height: | Size: 46 KiB |
Before Width: | Height: | Size: 57 KiB After Width: | Height: | Size: 57 KiB |
Before Width: | Height: | Size: 51 KiB After Width: | Height: | Size: 51 KiB |
Before Width: | Height: | Size: 103 KiB After Width: | Height: | Size: 103 KiB |
Before Width: | Height: | Size: 47 KiB After Width: | Height: | Size: 47 KiB |
Before Width: | Height: | Size: 29 KiB After Width: | Height: | Size: 29 KiB |
BIN
user/img/thirdparty_contact.png
Normal file
After Width: | Height: | Size: 46 KiB |
BIN
user/img/thirdparty_morale.png
Normal file
After Width: | Height: | Size: 32 KiB |