Skip to content
DataMiner DoJo

More results...

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
Search in posts
Search in pages
Log in
Menu
  • Updates & Insights
  • Questions
  • Learning
    • E-learning Courses
    • Empower Replay: Limited Edition
    • Tutorials
    • Open Classroom Training
    • Certification
      • DataMiner Fundamentals
      • DataMiner Configurator
      • DataMiner Automation
      • Scripts & Connectors Developer: HTTP Basics
      • Scripts & Connectors Developer: SNMP Basics
      • Visual Overview – Level 1
      • Verify a certificate
    • Video Library
    • Books We Like
    • >> Go to DataMiner Docs
  • Expert Center
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Markets & Industries
      • Media production
      • Government & defense
      • Content distribution
      • Service providers
      • Partners
      • OSS/BSS
    • Agile
      • Agile Webspace
      • Everything Agile
        • The Agile Manifesto
        • Best Practices
        • Retro Recipes
      • Methodologies
        • The Scrum Framework
        • Kanban
        • Extreme Programming
      • Roles
        • The Product Owner
        • The Agile Coach
        • The Quality & UX Coach (QX)
    • DataMiner DevOps Professional Program
      • About the DevOps Program
      • DataMiner DevOps Support
  • Downloads
  • More
    • DataMiner Releases & Updates
    • Feature Suggestions
    • Climb the leaderboard!
    • Swag Shop
    • Contact
    • Global Feedback Survey
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Deal Registration
  • >> Go to dataminer.services

InterApp API Question

Solved700 views17th January 2024automation scipt DevOps InterApp InterAppCall
5
Ryan Hepworth [DevOps Advocate]936 16th January 2024 0 Comments

Hi All,

We are looking at using InterApp to talk to an API and was wondering about a couple of points:

  1. Does InterApp support sending multiple requests from different panels/buttons at the same time to avoid having to lock the element whilst the request is being sent/processed?
  2. If sending 2 requests to make changes using the same panel/button (i.e. setting one input to paused and one to active) which is done through 2 separate API requests can that be sent at the same time or do you need to wait for a response before actioning the next request
  3. Is there any documentation that details the base mechanism on InterApp?

Thanks

Ryan

Ryan Hepworth [DevOps Advocate] Selected answer as best 17th January 2024

1 Answer

  • Active
  • Voted
  • Newest
  • Oldest
4
João Severino [SLC] [DevOps Catalyst]13.02K Posted 16th January 2024 3 Comments

Hi Ryan,

Regarding your questions

  1. You can send a single message or, what we call, an InterAppCall, which is like an array of messages that get sent at once.
    You can check the Factory classes next to each type to create them accordingly.
  2. If you use the single message option you most likely need to wait for the response but if you go for the InterAppCall approach you can send both at once and it will then be up to your executor to determine how they should be processed.
  3. You can find documentation on how to get started with InterApp at InterApp classes | DataMiner Docs
Ryan Hepworth [DevOps Advocate] Selected answer as best 17th January 2024
Ryan Hepworth [DevOps Advocate] commented 16th January 2024

Hi Joao,

Maybe I didn’t explain what I meant for point 1, so if we have 2 channels, with 2 different panels controlling them and want to set the inputs on the 2 individual panels, will InterApp queue the requests or do we need to lock the element until it has processed the first one and then we can do the next one.

So hit set on CH01, then hit set on CH02 and interapp queues the requests or hit ch01, lock the element so it can do the set, unlock and then do the same for ch02?

João Severino [SLC] [DevOps Catalyst] commented 16th January 2024

I do believe the requests should be queued as they should behave as set parameters triggering a QAction and it should wait for one QAction execution to finish before starting the next execution for the second request.

Jan Staelens [SLC] [DevOps Advocate] commented 16th January 2024

Note: InterApp messages are ‘queued’ per element. (they use the SetParameter Thread in the background)

So if you send a call to element 1 and element 2 at the same time, then there is no queue and there is no guarantee on when either call is processed.

If you send 2 calls both to element 1, then the calls are processed in order.

Please login to be able to comment or post an answer.

My DevOps rank

DevOps Members get more insights on their profile page.

My user earnings

0 Dojo credits

Spend your credits in our swag shop.

0 Reputation points

Boost your reputation, climb the leaderboard.

Promo banner DataMiner DevOps Professiona Program
DataMiner Integration Studio (DIS)
Empower Katas
Privacy Policy • Terms & Conditions • Contact

© 2025 Skyline Communications. All rights reserved.

DOJO Q&A widget

Can't find what you need?

? Explore the Q&A DataMiner Docs