Contact Methods¶
Before you start¶
This article delves into the contact methods available across different modules within Dsposal's Paperwork. Contact methods , once created, remain permanently recorded and cannot be deleted. However, they can be archived, preventing further selection when no longer applicable
What are contact methods?¶
Contact methods denote the means through which an organisation or individual initiated communication with you.
Completely optional
Contact Methods is a purely optional area of Paperwork. It comes down to individual organisations' business logic whether or not it is used.
Contact method details¶
Name | Description | Input type | Requirement Type |
---|---|---|---|
Contact Method | Contact methods denote the means through which an organisation or individual initiated communication with you. | text |
required |
Archived | Is this contact method still available for selection or has it been archived? | choice |
required |
Action | A button with a selector for actions related to this contact method. It provides a user interface element for initiating specific actions related to the contact method. | N/A |
N/A |
Actions¶
Each contact method has a number of actions that can be done to it. Not all are available all the time, the actions are dependent on the status of the contact method.
Action | Description |
---|---|
Manage |
Opens up available actions for the contact method. |
View / Edit |
Opens the contact method in edit mode, accessible when the method is active. |
Archive |
Archives the contact method, preventing selection in other Paperwork areas, available when the method is active. |
View |
Opens the contact method in view mode, applicable when the method is archived. |
Restore |
Restores the contact method, enabling selection in other Paperwork areas, available when the method is archived. |
Uses¶
Contact methods are used in the following areas of Paperwork:
The ERD(1) below shows where contact methods are used within Paperwork.
- An Entity Relationship Diagram is a type of diagram that lets you see how different entities (e.g. people, customers, or other objects) relate to each other in an application or a database.
erDiagram
Opportunities }o..o| contactMethods : contacts
Sales }o..o| contactMethods : contacts
contactMethods ["Contact Methods"] {
contactMethod text
archived boolean
}