The purpose of this section is to provide a space to document questions about Momentus, whether it be about what the software can do or troubleshooting steps. I also highly encourage checking the Momentus Support Center forums for question you might have regarding issues or the platform as well. I’ve found quite a few helpful threads with relating to issues either Admins have brought to me or things I have encountered myself.
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Momentus FAQ
Can Momentus be accessed by any web browser?
...
Below you will see a table providing some form of definition for the both Event and Service Order statuses. It is up to the Org to determine what statuses their users should be applying, since workflows change from CSU to CSU.
Status - Event | Description |
Request | This status can be used to denote an event has been received and no review has taken place. |
Pending | This status can be used to denote an event is under review or might need more information before approval. |
Waitlist | This status can be used to denote an event was requested for a space that might not be immediately available but might be in the future. |
Confirmed | This status can be used to denote an event has been reviewed and approved. |
Blocked | This status can be used to denote if spaces need to be blocked for any reason. i.e) Holidays, maintenance to spaces, etc. |
Settled | This status can be used to denote an event has been completed and all invoices have been paid. |
Ready to Invoice | This status can be used to denote an event has all service orders completed and it ready to be invoiced. |
Invoiced | This status can be used to denote an event has been invoiced but payment has not been applied or received. |
Unresolved | This status can be used to denote an event has not been completed due to any circumstances deemed by department/client. |
Cancelled | This status can be used to denote an event has been cancelled an no charges need to be collected. |
Declined | This status can be used to denote an event has been denied approval for taking place. Apply most relevant Cancellation Reason. |
Conflict | This status can be used to denote an event is requesting to take place but conflicts with another event for the same space and time. |
Cancelled with Charges | This status can be used to denote an event has been cancelled but charges need to be collected. |
Lost | This status can be used to denote an event was lost and apply most relevant Cancellation Reason. |
Archived | This status can be used to denote an event is no longer active and is being kept for record keeping. |
Status - Service Orders | Description |
Active | Active class statuses are available during the add and edit order process. |
Hold | Hold class statuses have no special restrictions and are for informational purposes only. This is often used for orders awaiting approval or payment. |
Closed | Closed class statuses are available during the close order process. You cannot edit or cancel closed orders. |
Cancelled | Cancelled class statuses are available during the cancel order process. You cannot edit cancelled orders. |
Cancelled With Fees | Cancelled with Fees class statuses are available during the registration cancel order process. When an order uses a status with this class, a pre-configured cancellation fee is automatically added to the order when it is cancelled. |
Settled | The service orders have officially been completed and paid.* |
Ready to Invoice | The service orders are ready to invoice.* |
*These statuses were created to assist in specific workflows a few departments have.
Momentus @ UT - Basic Troubleshooting Guide
...
If a requestor is having trouble accessing the OSB, there could be a few different reasons, and it is dependent on the error they receive. Here are some steps you can run through when attempting to troubleshoot:
| Info |
|---|
Please do not manually create a new account or contact for the user. If the user is affiliated with UT Austin, their account will be created or updated automatically when they log in via SSO. If you have created a manual user, please purge the account before moving on to the next troubleshooting steps. |
Confirming correct OSB links are being used – ensuring they are indeed a part of your college that should have access. They should always be accessing a SSO generated link that prompts them for their EID.
Changing account types when needed as some account assignments have to be manually managed. You can always review your OSB Access Charts for a refresher.
Cross-referencing Account/Contact Records and the User Account to make sure the information aligns with what the UT Directory has listed or what is in Workday/SIS. SSO is based on what information is being pulled from those sources, and if they do not match, this can cause log-in issues.
This is in In the Contacts section. : Verify the EID, email, and name are all correct. The UT Directory usually lists their information, however. However, you can also confirm with the requestor what their email is in the SIS or Workday.
...
This is in In the Users section. Be sure to clear our : Clear out the filters before you search since it will default to the view you use. Here, you will want to make sure the Org matches your Organization, and the email matches what is seen in the UT Directory.
...
Clearing Clear out the User the User field in the account/contact record, savingsave it, and then having have them try to log in again.
...
Making Make sure the Internet Logon check box is selected.
Activating a personnel account in the contact/account record.
Making Make sure the Communications field in the contact record only has the email information of the contact in question. Incorrect merges can cause issues, and emails that don’t belong to one another can get mixed and cause log-in issues.
After these fixes are attempted, it’s always a good reminder to have their them clear their cache or try to access the platform through an incognito window.
...