Laserfiche WebLink
Agenda Conversion Data Matrix <br />Meeting Type Configuration <br />Meeting Type <br />Default Location <br />Default Time <br />I Default Time to Lock meeting <br />Meeting Outline <br />Meeting Outline Numbering <br />Information Box Configuration <br />Meeting Templates (Agenda, Minutes, Summary) <br />Packet markup/overlay configuration <br />Meeting Security <br />Users <br />Department <br />Permissions <br />Meeting Attendees <br />Attendee Names <br />Attendee Title/Position <br />REV: 01-09-1815 <br />ATTY/AGR.2018.001/Hyland Onbase ACMS <br />Converted <br />to OnBase <br />Yes <br />No <br />No <br />No <br />Yes <br />Yes <br />Contract #: BSA -EU -14546-15060771 <br />Notes/Comments <br />Default Location is not a meeting type <br />property in OnBase. The default <br />location can be added to your template <br />to acco7lish the same effect. <br />Default Time is not a meeting type <br />property in OnBase. The default time <br />can be added to your template to <br />accomplish the same effect. <br />Item creation restrictions are handled in <br />OnBase Workflow. <br />Information boxes are not supported in <br />No OnBase at this time. <br />Yes <br />These settings do not automatically <br />migrate but you can configure many of <br />these options in OnBase using the <br />No Packet configuration interface. <br />Yes <br />No <br />No <br />Yes <br />Yes <br />Page 47 of 51 <br />users can De migrated from SIRE to <br />OnBase. Most customers choose to start <br />fresh with security when migrating from <br />system to system to ensure only active <br />users and current access policy is in <br />Wce in the new system <br />e SIRE Departments and the OnBase <br />Groups and Ownership Groups are too <br />different to migrate. It is best practice <br />to setup security using the new systems <br />features and options instead of trying to <br />manipulate the old security behavior <br />into the new behavior. <br />The SIRE permissions and the OnBase <br />permissions are too different to migrate. <br />It is best practice to setup security using <br />the new systems features and options <br />instead of trying to manipulate the old <br />security behavior into the new behavior. <br />