UOF (U-Office Force)
e-Excellence
System integration
Lets the Agent use UOF e-signoff as each end user: see which forms there are, file and track requests, and approve or return the ones waiting for that person.
Connection routes
About the routes →FDE Rune
API key or tokenWhile the deployment is being designed, the FDE Agent files and approves a test request for each form on the UOF test environment, and writes down how to fill in each form. Needs an applicant and an approver account there.
Connector
No account neededEach end user signs in to UOF in the browser beside the conversation, and the Agent files, tracks and approves requests as that person. No UOF keys are stored on the platform, and each new conversation needs a new sign-in.
Documentation
The Agent works in UOF e-signoff as the end user who is talking to it. It reads which forms there are and where each request is in its approval flow. It also files new requests, approves or returns requests that wait for that end user, and withdraws that end user's own requests. Before each of these changes, the Agent shows the content and waits for the end user to confirm.
This is for the first-generation UOF from e-Excellence. UOF X is a different product.
What you need
- UOF (first generation), with a test environment and a production environment.
- A UOF account for each end user. Each end user signs in to UOF with their own account.
- Network access from the platform to the UOF site. If UOF is open only on the internal network, the IT department of the organization must allow access.
- A person who knows what the fields on each form mean, to answer the questions of the FDE Agent.
Rollout consultation
e-Excellence and U-Office Force (UOF) are trademarks of their owner.