Updating a Meeting Template - Configure Meeting Settings - Configuring Automatic Resolution Numbering

Geeta Nagpal
Geeta Nagpal
  • Updated

The following steps assist Administrators in activating and setting up Automatic Resolution Numbering as a self-service feature. 

Menu> Meeting Templates > Edit template> Configure Meeting Settings> Motion>  Enable Resolution Numbering

 

Screenshot_138.jpg

 

ZoneDescription 
1- Enable Resolution NumberingA toggle switch is used to enable the Automatic Resolution Number, which will appear in meeting, search, and reporting features once configured.
2-  Numbering Format

The text describes how numbers are displayed during the meeting. Administrators can choose from a selection of available variables, with the Sequence number variable being the default option, as it indicates the order of the number. Additionally, custom text can be included, allowing for up to 1000 characters as required.

For example, a resolution number of 2025 - 003 will use the following variables:

{{MeetingYear}} - {{SequenceNumber}}

Insert Variables

Administrators can select from any of the variables to add to the Numbering Format box.

VariableAppears as 
Meeting TypeFull name of Meeting Template
Meeting IdentifierDisplays abbreviated Meeting Template name (ie CM, COW, BOD).
Meeting YearAppears as current year ( 4 digits)
Meeting MonthAppears as current month (2 digits) 
Meeting DayAppears as Meeting Day ( 2 digits) 
Sequence NumberDisplays the next number in the sequence. In the event the number is changed in a meeting, the counter will display the correct number in sequence in the Meeting Template.

 

3- Sequence NumberAllows Administrators the ability to reset the counter as required. In the event the sequence is overridden in the meeting, administrators can  change the sequence to reflect the correct number to be assigned.
4- Number of Digits Specifies the count of digits utilized for displaying the Sequence number. For instance, a format of 003 consists of 3 digits in the textbox.

 

Comments

0 comments

Article is closed for comments.