>

Momentus Connect inconsistent in modules/features between element mapping and role access window

Investigating
Nicole Loh

Zendesk Ticket: https://ungerboeck.zendesk.com/agent/tickets/387565
Account: Victorian Convention and Event Trust
Region: APAC
Articles used in your research: No articles available
 
General
Business impact if not resolved: This may cause issues with auditors during auditing season as there is a mismatch of modules/features in the system, it is also confusing for admins as they aren't sure whether they are granting the correct access
Short Summary of issue (issue description): Momentus Connect inconsistent in modules/features between element mapping and role access window
Macro Vertical: Convention Centers
 
Debug Environment:
Customer DB Location: Hosted
Database: QESample261
Server: 10.98.101.165\QE_ENVIRONMENT,1434
Version: 26.1.9663.33395 (20260616)
V30 Link: https://qe.ungerboeck.com/26_1/app85.cshtml
User Login: nicole // nicole
 
Recreation Steps:

  1. Login with nicole // nicole
  2. From the main menu, search for element mapping.
  3. Type in momentus connect in the element field.
  4. Notice that the Module/Feature listed is Momentus Connect- Administration, Professional Features - System Administration. The element ID for this is 7558.
  5. Go to the main menu and search for role access. Filter to user Nicole Loh (NICOLE), type in momentus connect in the element field > Search.
  6. Notice that this action is also listed under Express Features - Basic Express Functionality which was not listed in the element mapping window. 
     

Observed vs. Expected Results: We expect element mapping and role access to have consistent listings of elements to their modules and features. 
What does the client want to accomplish: Client needs the system to have clarity on which module/feature each element belong to

Comments

6 comments

Date Votes
  • Nicole Loh

    Satya Ram Nukala Mike Schepker Pieter Fourie Am I right that both module/feature in role access and element mapping should match? In the above screenshot, you can see that it can be deceiving because in element mapping, there is no mention of it being available to express users, however in role access it shows as available to user in an express feature/module. 

  • Satya Ram Nukala

    Nicole Loh I would think the same, they should align. Haven't seen any scenarios of mismatch.

  • Seth Halvaksz

    This has to do with licensing, so we'll need to research this.

    I understand the main question is what is “Basic Express Functionality” (7558) and why is it visible on “Role Matching” but not under under the Element Mapping.

  • Seth Halvaksz

    Nicole, we've looked into this, but not sure why this is showing up.

    At this point, i'm trying to understand is this is worth the additional time to investigate. What is the business impact to the customer for this?

    I did confirm there are 3 Momentus Connect elements that are showing under Basic Express.  So its something related to Momentus Connect.

  • Nicole Loh

    Seth Halvaksz I've asked the customer what the impact is to their business and below is their response: 


    Hello,

    Momentus Connect is under a system administration/utilities in the Main Menu but it's actually a part of the Express User features. To get around this I had to create a new role to replicate "All Users" and assign the FP&A team then remove them from the All Users role because it denies Momentus Connect.

    Nightmare. 

    Now they have introduced roles in Connect which means I have to go undo what I've mentioned above.

    This has created unnecessary work for everyone.

    Cheers,
    Adriana

  • Seth Halvaksz

    Nicole Loh It sounds like she was trying to control access to Momentus Connect with roles, and that was the challenge.  Now is now setting up roles in Connect to control access.

    I'm also copying Victor Nogales Junior so he is aware.

Please sign in to leave a comment.

Didn't find what you were looking for?

New post