Activity and Inventory Sharing

The Activity and Inventory Sharing feature enables users to share or transfer activities and inventory items directly within a Collaboration chat. Recipients can review the shared information and explicitly accept or reject the transfer, creating a clear and traceable audit trail.

Business Benefits:
  • Faster workload balancing: Move jobs and parts inline in the chat so the next available or closer resource can take over without dispatcher back and forth.
  • Higher first-time fix: Ensure the right mobile worker or part reaches the job on the first attempt by transferring ownership or stock in context.
  • Lower coordination overhead: Eliminate phone calls and side channels - decisions, transfers, and confirmations all remain in the same thread.
  • Clear audit and accountability: Accept, reject, and transfer outcomes create a traceable record for performance reviews and root cause analysis.
  • Risk control through permissions: Only authorized roles can move activities or stock, reducing compliance issues and inventory shrink risks.
Functional Description:
  • Activity shares can be informational; transfers require recipient acceptance.
  • Inventory transfers check ownership and item rules, and all actions are logged in the thread.

Use Cases

Helpdesk in Collaboration supports a variety of operational scenarios across the field service landscape. Here are some examples:
  • SLA rescue - reassignment to the nearest qualified mobile worker

    A job is about to breach its SLA window. Dispatch shares the activity in chat, confirms availability and skills, and then offers a transfer to the nearest qualified resource. The recipient accepts, the system updates ownership, and the thread retains the reason and time of transfer for audit. The customer ETA is adjusted in the normal process.

  • Specialist assist - hand back to original mobile worker

    A mobile worker encounters a complex step and shares the activity with a specialist for quick guidance, including photos and notes in the thread. If on-site ownership needs to change temporarily, the desk transfers the activity to the specialist. Once the issue is resolved, the specialist transfers it back. The thread holds the troubleshooting trail and both transfer timestamps.

  • Cross-van parts move for same-day fix

    A mobile worker is missing a critical part. The desk opens a one-to-one chat with a nearby colleague who has the required stock, confirms item details, and initiates an inventory transfer. The receiving mobile worker accepts; stock counts update, and the chat captures the part, quantity, and acceptance event. The original job proceeds without reschedule.

  • Mid-shift offboarding or emergency coverage

    When a mobile worker must leave mid-shift, the supervisor shares the remaining activities with available candidates and transfers each job with a short note describing priority and customer constraints. Recipients accept or reject quickly, revealing any coverage gaps. The thread serves as the handover record, and dispatch uses it to confirm any customer communication needed.

  • End-of-day rollover and next-day staging

    Late in the day, the supervisor shares partially completed activities and any required parts with the late or next shift lead. The lead transfers jobs and coordinates inventory transfers in one-to-one chats so that the next shift starts with the right materials. Accept and reject responses and transfer notes remain in the thread for a clean morning hand off.

Configure User Access

Proper setup ensures that users can securely transfer activities and inventory with accurate tracking.
  1. Navigate to Configuration > User Types.
  2. Enable one or both permissions as required:
    • Activity Move via Chat
    • Inventory Move via Chat
  3. Verify that visibility settings allow sharing between intended users.
  4. Review routing or timeout settings with the routing administrator to align with assignment logic.
  5. Train users on acceptance, rejection, and follow-up processes.

Integrate and Synchronize

To keep data consistent between Collaboration and core Oracle Fusion Field Service systems:
  • Activities: Create, update, cancel, or complete activities using REST APIs.
  • Inventory: Set, update, delete, or reassign inventory items using REST APIs.
  • Context Posting Using REST APIs: Posts activity or inventory information directly into an existing Collaboration chat.
    Example:
    POST/rest/ofscCollaboration/v1/chats/{chatId}/messages
    Content-Type: application/json
    {
      "text": "Please take this job if you’re nearby.",
      "attachment": { "type": "activity", "id": "ACT-98765" }
    }

For more information, see Integration with Collaboration.

Transfer Activities and Inventory

You can share or transfer activities and inventory directly from Collaboration, ensuring both coordination and accountability occur in a single, traceable thread.

Share or Transfer an Activity:
  1. Open the Collaboration window.
  2. Choose an existing chat or start a one-to-one chat with the target user.
  3. In the message box, click Share Activity or drag the activity directly into the chat window.
  4. Select Transfer Activity if you are changing ownership.
    Note: You must have visibility to the recipient to share or transfer an activity.
  5. The recipient receives a message with Accept and Reject options.

    Once accepted, ownership is updated automatically.

Share or Transfer Inventory:
  1. Open a one-to-one chat with the target user.
  2. Click Inventory Details → Transfer Inventory.
  3. Enter the item details, quantity, and optional note. You can also drag an inventory item into the chat to share it instantly.
  4. Click Send to complete the request.
  5. The recipient receives a message with Accept and Reject options.
    On acceptance, the inventory ownership is updated, and the event is logged in the thread.
    Note:
    • Transfers are permitted only if the user has the necessary permission and the item belongs to their pool.
    • The application validates ownership, item type, and visibility before transferring.
    • If the conditions are not met, an error message appears, and the transfer is not completed.