HOME
Copy
PDF Export
Print Print
FeedBack
Expand All
  • Stemmons Central User Manual
    • Overview
    • Stemmons Central User Interface
    • Home
    • Cases
    • Departments
    • Entities
      • Entities System Overview
      • Entities Stemmons Application Architecture
      • Entities System Data Architecture
      • Entities System Configuration
      • Entities System Best Practices
      • HTML Template for Entities
      • HTML Tag Body Template for Entities
      • Tag Control for view control in Entities
      • Entities Calculation Field
      • Entities - Entity Role to Employee Association
      • Entity to Entity Role Relationship
      • Entities Cases Relationship through External Datasource
      • Entities Quest Relationship via External Datasource
      • Extensible Grid in Entities
      • Subscription to Hopper-Entities
      • System Code for Entities Publishing Purpose
      • Kanban View for Entities
      • Recipe Builder
      • External Entities
      • Security Scenarios for Diffrent Users in Entities Application
      • Field Level Security for Entities
      • Entities - Entity to Entity Role Association
      • Entities Dynamic Template
      • Entities Job Aid
      • Entities Portal
      • Email to Entities
      • Entity Overlay
      • Entity Merging
      • Entity Copy
      • Entities Hopper
      • Unassign Item button in Entities
      • Entity Conversion
      • Entities Custom Query
    • Facts
    • Standards
    • Quest
    • Cast (Central Automation System)
    • Common Language Gateway (CLG) /Common Data Resource
    • External User
    • Import Tools
    • Stemmons Web API
    • Migration Tool
    • ULS (Unified Logging System) Log Viewer
    • BlockChain-Trigger
    • Blockchain Trigger API Matrix Table
    • Custom Branding
    • Stemmons Search
    • Appendices
    • Updoc
    • Passive Trigger
    • Stemmons Central Mobile Application Login Process
    • How to Configure SSO with a SAML 2.0 in Stemmons Cloud Authentication Handler
    • Stemmons Cloud Authentication Handler
    • Web Form to Cases
Entities Hopper


Hopper is a concept of allowing group of users to manage cases/entities/quest forms that are assigned/responsible by a group of users instead of to individual.

The users can subscribe to the Hopper and would receive notifications on the cases the same way individual user receive notification on case assignment. The Hopper subscribers also see the Hopper List on the Home Page or Entity Origination Center.

Hoppers are being created/maintained in Entities Application under Entity Category Type: System. Entity Type Name: Hopper. The below are the available fields in the Hopper Entity type:

  • Hopper Name: Name of Hopper.
  • Hopper Description: Description of Hopper.
  • System Code: Create a System Code for the Hopper to create a fictitious identity for the Hopper. This is analogous to the User Name (or SAM Account) for individuals, allowing the system to treat the Hopper as a person. The syntax used by the system is “HOPPER [SYSTEM CODE]’.
  • Email Address: Email address to for notification purposes associated with a Hopper.
  • Suppress Auto Alert: If checked, suppress alert emails.
  • Is Active: Check if Hopper is active.
  • Hopper Owner: System ID for Hopper Owner. All active Hoppers should have a Hopper Owner.
  • Help URL: Future use for context sensitive help.
  • Application Name: The Application of the Hopper (Cases, Entities, and Quest). This is a multi option. A Hopper can be created for one or more applications.

Note: Once the Hopper is created, the hopper will be automatically synced to the Configurations and allow Admin User to associate the Hopper to the Case Type, Entity Type, or Quest Item (as a Default Hopper, or assignment configurations in Cases Email Command, Quest Form Threshold Assignment, etc.).