3 results found

1. Add the Business Organization to the Move Center

   We have currently separated into 3-different business entities. To improve the Move Requests Center so you can quickly see which Business (or Business Unit) each person belongs to—without drilling into every record—especially during peak onboard/exit periods.
   Proposed Change Summary
   • Add a new header/column: Business
   • Column position: between Description and Requester
   • Data source: “User Allocations” — use the “Business” field if present; otherwise fall back to “Business Unit”
   • Behavior: Display the employee’s current/active business at time of viewing; update dynamically if allocations change
   • Goal: Reduce time spent opening individual requests during high-volume periods
   Recommended Implementation Approach
   1. Clarify data source and precedence
   • Primary field: Business
   • Fallback field: Business Unit (if Business is null)
   • Edge cases: Multiple active allocations—deterministic rule needed (e.g., most recent effective date or primary flag)
   2. Modify list view schema
   • Insert the Business column between Description and Requester in the Move Requests Center grid
   • Enable sorting and filtering on Business to batch actions by Business
   • Allow column to be added to exports
   3. Data retrieval logic
   • Join/lookup User Allocations by Employee ID for current effective allocation
   • Apply precedence: Business → Business Unit
   • Cache lightly for performance, but refresh on list reload to reflect recent changes
   4. UX considerations
   • Tooltip/hover on Business to show source field and effective date (e.g., “Business via User Allocations, effective 2025-01-15”)
   • If multiple allocations exist, show the chosen one and an icon indicating multiple—click opens detail
   • Preserve column in saved views so teams can set “Onboards by Business” and “Exits by Business” views
   5. Performance safeguards
   • Use server-side filtering and pagination to avoid slowdowns for large queues (20–40+)
   • Retrieve Business in the main query to avoid N+1 lookups
   • Index User Allocations on Employee ID and Effective Date
   6. Data quality and governance
   • Define a single system of record for Business
   • Set validation to prevent empty Business and Business Unit for active users
   • Add an exception state (e.g., “Unassigned”) with a reconciliation dashboard

   We have currently separated into 3-different business entities. To improve the Move Requests Center so you can quickly see which Business (or Business Unit) each person belongs to—without drilling into every record—especially during peak onboard/exit periods.
   Proposed Change Summary
   • Add a new header/column: Business
   • Column position: between Description and Requester
   • Data source: “User Allocations” — use the “Business” field if present; otherwise fall back to “Business Unit”
   • Behavior: Display the employee’s current/active business at time of viewing; update dynamically if allocations change
   • Goal: Reduce time spent opening individual requests during high-volume periods
   Recommended Implementation Approach… more

   •  

   •  

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  System Integration & Data Flow  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Impactful You must login first! Fundamental You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Enable PATCH/PUT Methods for Assets API Endpoint

   The ManagerPlus API v2 currently supports GET and POST for /Assets, but returns HTTP 405 for PATCH/PUT methods. This prevents programmatic updates to existing asset records.

   Use Case:
   We need to bulk-update asset fields (descriptions, statuses, etc.) for our 2,400+ asset inventory without manual UI edits.

   Requested Feature:
   Enable PATCH or PUT on /api2/Assets/{assetKey} to allow updating existing assets via API.

   Expected Behavior:
   PATCH /api2/Assets/{assetKey}
   {
   "Description": "Updated value",
   "StatusId": "ACTIVE"
   }

   Would enable automated data quality workflows and reduce manual administrative overhead for maintaining accurate asset records.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  System Integration & Data Flow  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Impactful You must login first! Fundamental You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Under Review  ·  AdminRobbie.Brannen@eptura.com (Senior Product Manager, Eptura) responded

   Our Product team is currently reviewing your idea. We may contact you if we need additional information or clarification. While not every idea will be added to our product roadmap, we carefully evaluate each submission and yours will receive full consideration.

3. API Access to Complete Asset Field Schema

   We need the ability to make API calls that retrieve or set any and all fields associated with asset records, including standard fields, custom fields, budget fields, hierarchy fields, and any other asset properties. Currently, the API documentation doesn't clearly expose all available fields or provide comprehensive endpoints for accessing the full asset schema. This would enable:

   -Bulk operations on all asset attributes programmatically

   -Complete asset records in API responses (not truncated/limited)

   -Field discovery without reverse-engineering existing assets

   -Integration with external systems that need to read(at least)/write all asset data (including status/state)

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  System Integration & Data Flow  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Impactful You must login first! Fundamental You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Deferred  ·  AdminRobbie.Brannen@eptura.com (Senior Product Manager, Eptura) responded

   Thank you for your suggestion—this idea has merit and aligns with our broader strategy. However, due to other priorities, we are unable to pursue it at this time. We’ll keep it on our radar and revisit it when the timing is right or if we see increased interest from our customer community.