In order for automatic signature objects to be created in M-Files, aliases must be created for the new object type as well as for the required property definitions. The aliases are used for creating objects at the time of signing. If you are using the Electronic Signatures module, these definitions are already available. Otherwise, you should create the metadata definitions below in order to activate the separate signature objects.
Create a new object type and name it, for example, the Signature object type. In the advanced settings, specify the object type alias:
M-Files.QMS.Signature.ObjectType
When you have created a new object type, M-Files automatically creates an equivalent property definition. Select this property definition in the property definitions and add the following alias:
M-Files.QMS.Signatures
In addition to this, add the aliases listed below:
| Identifier | |
|---|---|
| Alias | M-Files.QMS.Signature.Identifier |
| Data Type | Text |
| Description | The identifier property is added to the electronic signature when the electronic signature object is created. The identifier property value is specified in the electronic signature settings in M-Files Admin. |
| Reason for signature | |
|---|---|
| Alias | M-Files.QMS.Signature.Reason |
| Data Type | Text |
| Description | A brief heading-level description for the signature. |
| Signature meaning | |
|---|---|
| Alias | M-Files.QMS.Signature.Meaning |
| Data Type | Text (multi-line) |
| Description | A description enabling the signer to understand what is being approved. |
| Signer | |
|---|---|
| Alias | M-Files.QMS.Signature.Signer |
| Data Type | Choose from list (select the Users value list) |
| Description | The vault user electronically signing the state transition. |
| User | |
|---|---|
| Alias | M-Files.QMS.Signature.User |
| Data Type | Choose from list (select the Users value list) |
| Description | The vault user to whose identity the signature is bound when the signature is used for moving an assignment to a terminal state, such as Completed, Accepted, or Rejected. |
You can freely name the compulsory property definitions mentioned above, but you should use the most descriptive names possible, since this information is shown in the metadata of the signature object.
You can also create various optional property definitions for the signature object. For example, you may want to create a new property definition for additional signature information with the data type Text (multi-line) and add the following alias:
M-Files.QMS.Signature.AdditionalInfo
The rest of the optional properties are listed below:
| M-Files.QMS.Signature.Signer.Name | |
|---|---|
| Data Type | Text |
| Description | Contains the full name of the signer. |
| M-Files.QMS.Signature.Signer.Account | |
|---|---|
| Data Type | Text |
| Description | Contains the M-Files account name of the signer. |
| M-Files.QMS.Signature.LocalTimestampText | |
|---|---|
| Data Type | Text |
| Description | The local time of the signature as text, including the timezone information. |
| M-Files.QMS.Signature.UTCTimestampText | |
|---|---|
| Data Type | Text |
| Description | The UTC time of the signature as text, including the timezone information. |
| M-Files.QMS.Signature.UTCTimestamp | |
|---|---|
| Data Type | Timestamp |
| Description | The UTC timestamp of the signature. |
| M-Files.QMS.Signature.Date | |
|---|---|
| Data Type | Date |
| Description | The signature date in local (server) time. |
| M-Files.QMS.Signature.FromState | |
|---|---|
| Data Type | Choose from list (select the States value list) |
| Description | The workflow state prior to the state transition. Available only when signing state transitions. |
| M-Files.QMS.Signature.ToState | |
|---|---|
| Data Type | Choose from list (select the States value list) |
| Description | The workflow state after the state transition. Available only when signing state transitions. |
| M-Files.QMS.Signature.StateTransition | |
|---|---|
| Data Type | Choose from list (select the State Transitions value list) |
| Description | The workflow state transition that has been executed. Available only when signing state transitions. |
You can also create so-called empty signature objects and use them to monitor which signatures have not yet been signed and which signatures have already been executed. You can utilize these empty, executed, and invalidated signature objects creating different classes for the signature object type.
Here are the aliases which, if specified for classes of the Signature object type, are utilized by M-Files in various phases of electronic signing:
M-Files.QMS.Signature.Class.Empty
M-Files.QMS.Signature.Class.Executed
M-Files.QMS.Signature.Class.Invalidated
Metadata definitions (object type and property definitions) created for the automatic signature object should be secure; it should not be possible to create signature objects manually or change their metadata. Also the property definition that binds the signed object to the signature must be secure. If you are using M-Files QMS, these definitions are already available.
When you have created the necessary definitions and chosen creation of a separate object for the signature, the object will be automatically created after signing.
The name of the signature object is created automatically from the signature reason, signer and timestamp.
Other metadata for the signature object are created automatically on the basis of the signature definitions.