Glossary - Revision history

Ascentadmin at 14:46, 18 February 2025

2025-02-18T14:46:59Z

Ascentadmin at 14:44, 18 February 2025

2025-02-18T14:44:11Z

Ascentadmin at 14:42, 18 February 2025

2025-02-18T14:42:56Z

Ascentadmin at 14:37, 18 February 2025

2025-02-18T14:37:09Z

Ascentadmin at 14:35, 18 February 2025

2025-02-18T14:35:17Z

Ascentadmin at 14:33, 18 February 2025

2025-02-18T14:33:45Z

Ascentadmin at 11:15, 17 October 2024

2024-10-17T11:15:28Z

Ascentadmin at 16:48, 12 August 2024

2024-08-12T16:48:31Z

Ascentadmin at 16:02, 17 July 2024

2024-07-17T16:02:52Z

Ascentadmin at 15:55, 17 July 2024

2024-07-17T15:55:16Z

@@ Line 2,400: / Line 2,400: @@
 |-
-| <div id="essage_DefaultTargetType">&nbsp;</div>
+| <div id="Message_DefaultTargetType">&nbsp;</div>
 |-
 | colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: Default Target Type</div>
@@ Line 2,430: / Line 2,430: @@
+|
      The last date active messages will be displayed.  Note: All messages are removed after 72 hours.
 |-

@@ Line 2,414: / Line 2,414: @@
+|
      Defines a specific target for a message.  Targets are Users, Servicers or Dispatch groups.
 |-
 | <div id="Message_StartDate">&nbsp;</div>
@@ Line 2,446: / Line 2,447: @@
      When checked the message window will automatically display when users load the Dashboard. When not checked the use will have to click a button to open the messages window.
 |-
 | <div id="MLTE_Servicer">&nbsp;</div>

@@ Line 2,392: / Line 2,392: @@
 |-
-| &nbsp;
+| <div id="Message_TargetType">&nbsp;</div>
 |-
-| Messages: Target Type
+| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: Target Type</div>
 |-
+|
@@ Line 2,400: / Line 2,400: @@
 |-
-| &nbsp;
+| <div id="essage_DefaultTargetType">&nbsp;</div>
 |-
-| Messages: Default Target Type
+| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: Default Target Type</div>
 |-
+|
      Defines the type of target audience for the message as the default value for new messages.
 |-
-| &nbsp;
+| <div id="Message_Target">&nbsp;</div>
 |-
-| Messages: Target
+| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: Target</div>
 |-
+|
      Defines a specific target for a message.  Targets are Users, Servicers or Dispatch groups.
 |-
-| Messages: Start Date
+| <div id="Message_StartDate">&nbsp;</div>
 |-
-| &nbsp;
+| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: Start Date</div>
 |-
+|
      The first date active messages are displayed.
 |-
-| &nbsp;
+| <div id="Message_EndDate">&nbsp;</div>
 |-
-| Messages: End Date
+| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: End Date</div>
 |-
+|
      The last date active messages will be displayed.  Note: All messages are removed after 72 hours.
 |-
-| &nbsp;
+| <div id="Message_FieldComplete">&nbsp;</div>
 |-
-| Messages: Field Complete
+| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: Field Complete</div>
 |-
+|
      When checked an automatic message will generate when jobs are changed to the Field Complete status.
 |-
-| &nbsp;
+| <div id="Message_AutoShow">&nbsp;</div>
 |-
-| Messages: Auto Show Messages
+| colspan="1" style="width: 1538px;" | <div class="fieldHeader">Messages: Auto Show Messages</div>
 |-
+|
      When checked the message window will automatically display when users load the Dashboard. When not checked the use will have to click a button to open the messages window.
 |-
 | &nbsp;

@@ Line 2,398: / Line 2,398: @@
+|
      Defines the type of target audience for the message.
 |-
 | &nbsp;
@@ Line 2,403: / Line 2,404: @@
 | Messages: Default Target Type
 |-
-| &nbsp;
 |-
 | &nbsp;
 |-
 | Messages: Target
 |-
+|
      Defines a specific target for a message.  Targets are Users, Servicers or Dispatch groups.
 |-
@@ Line 2,421: / Line 2,422: @@
+|
      The first date active messages are displayed.
 |-
 | Messages: End Date
 |-
+|
      The last date active messages will be displayed.  Note: All messages are removed after 72 hours.
 |-
 | Messages: Field Complete
 |-
+|
      When checked an automatic message will generate when jobs are changed to the Field Complete status.
 |-
@@ Line 2,443: / Line 2,446: @@
+|
      When checked the message window will automatically display when users load the Dashboard. When not checked the use will have to click a button to open the messages window.
 |-
 | &nbsp;

@@ Line 2,396: / Line 2,396: @@
 | Messages: Target Type
 |-
-| &nbsp;
 |-
 | &nbsp;
@@ Line 2,412: / Line 2,413: @@
+|
      Defines a specific target for a message.  Targets are Users, Servicers or Dispatch groups.
 |-
 | Messages: Start Date
@@ Line 2,419: / Line 2,421: @@
+|
      The first date active messages are displayed.
 |-
 | Messages: End Date
@@ Line 2,426: / Line 2,429: @@
+|
      The last date active messages will be displayed.  Note: All messages are removed after 72 hours.
 |-
 | Messages: Field Complete
@@ Line 2,433: / Line 2,437: @@
+|
      When checked an automatic message will generate when jobs are changed to the Field Complete status.
 |-
 | Messages: Auto Show Messages
@@ Line 2,438: / Line 2,443: @@
+|
      When checked the message window will automatically display when users load the Dashboard. When not checked the use will have to click a button to open the messages window.
 |-
 | &nbsp;

@@ Line 18: / Line 18: @@
+|
      Indicates that the record can be used to produce results.
 |-
 | <div id="AgreementAnnvDate">&nbsp;</div>
@@ Line 98: / Line 99: @@
      Indicates if the agreement covers parts transactions.
 |-
@@ Line 122: / Line 124: @@
+|
      The total deferred revenues posted to date.
 |-
 | <div id="AgreementEstDate">&nbsp;</div>
@@ Line 2,388: / Line 2,391: @@
      The three digit prefix to use when auto-numbering new equipment records.
 |-
 | <div id="MLTE_Servicer">&nbsp;</div>

@@ Line 18: / Line 18: @@
+|
      Indicates that the record can be used to produce results.
 |-
@@ Line 26: / Line 33: @@
+|
      Indicates the amount percent of increase for the agreement renewal.
 |-
@@ Line 58: / Line 73: @@
+|
      The person that should be contacted concerning the agreement.
 |-
@@ Line 66: / Line 122: @@
+|
      The total deferred revenues posted to date.
 |-
@@ Line 146: / Line 217: @@
+|
      Agreement numbers are used to identify agreements. On the Job forms it indicates the agreement that may be used to cover transactions. On the PM Schedule form it indicates the agreement that is attached to the schedule.
 |-
@@ Line 205: / Line 284: @@
          By Site: The contract amount is a total of all site prices on the agreement. Each site can have a different price.
          By Equipment: The contract amount is a total of all equipment prices on the agreement. Each equipment record can have a different price.
 |-
@@ Line 279: / Line 366: @@
+|
      The salesperson that should be assigned to the invoices when billing occurs.
 |-

@@ Line 2,636: / Line 2,636: @@
+|
      The time the technician is scheduled to do the work.
 |-

@@ Line 1,963: / Line 1,963: @@
 |-
+|
-     The primary servicer for the job. New jobs will automatically use the primary servicer.
+     The primary servicer for the job. New jobs will automatically use the primary servicer. Set up on the site level servicer #1
 |-

@@ Line 1,923: / Line 1,923: @@
 |-
+|
-The job's main contact telephone number
+    The job's main contact telephone number
 |-