Skip to main content
Open

Enable XML Parameter Access in Layout & Default Logic

Related products:Indicium Service Tier
Harm Horstman
Michael
Mark Jongeling
szonnenberg
Tom van Druten
+36
  • Harm Horstman
    Harm Horstman
  • Michael
    Michael
  • Mark Jongeling
    Mark Jongeling
  • szonnenberg
    szonnenberg
  • Tom van Druten
    Tom van Druten
  • John Lunenburg
    John Lunenburg
  • Geurt
    Geurt
  • Erwin Ekkel
  • Freddy
    Freddy
  • Ricky
    Ricky
  • Arie V
    Arie V
  • Rafal Zaluski
    Rafal Zaluski
  • g.c.d.vanderschoot
  • J. de Lange
    J. de Lange
  • mperrott
    mperrott
  • W. Bos
  • Marijn Metzlar
  • Jan Egbert Muurman
  • Suleyman
  • avdbrand
  • Elco van der Veen
  • Jefferson Delacruz
  • Rick
  • Shawn Adrian Diño
  • WarrenM
  • Jason Philip A Mortera
  • Rucha Naik
    Rucha Naik
  • Hidde Jan
  • Lars_P
  • Christian Schmidtchen
    Christian Schmidtchen
  • Marius Korff
    Marius Korff
  • Hans Pot
  • Richard Elderman
  • rbiram
    rbiram
  • Gabriela Andes
    Gabriela Andes
  • Karin
  • Balazs Szeder
    Balazs Szeder
  • Ruben_Kwant
  • Vince D
  • srpanayas
  • jp vacunawa

Opportunity:
Our platform already empowers users to build dynamic tasks, but we can make it even more powerful. By allowing XML parameter access in both layout and default logic, we open the door to smarter, more adaptive task designs—without workarounds.

Why This Matters:
Imagine tasks that:

  • Auto-adapt to their context (e.g., show/hide fields based on row counts or parameter values).

  • Simplify complex workflows by replacing redundant "helper" tasks with built-in logic.

  • Boost reusability—one task can serve multiple purposes (single-row edits vs. batch processing) while keeping models clean.

Benefits:
✨ Sleeker Models – No more placeholder tasks just to pass values.
✨ Richer User Experience – Interfaces respond intelligently to data.
✨ Easier Maintenance – Fewer tasks = fewer bugs and faster updates.

Did this topic help you find an answer to your question?

4 replies

Jeroen van den Belt
Administrator
Forum|alt.badge.img+9

Hi ​@Maarten,

Can you elaborate a bit more on what you mean by “allowing XML parameter access”. Has this something to do with the multirow XML parameter, or do you mean something else? We don't fully understand. Thank you!


Jeroen van den Belt
Administrator
Forum|alt.badge.img+9
NewNeeds feedback

Forum|alt.badge.img+4
  • Author
  • Vanguard
  • 24 replies
  • May 14, 2025

@Jeroen van den Belt  Yes i mean the MultiselectParameterID from the extended properties. This currently only allows you to have the data of that task parameter after task execution.

By accessing the data in the default and layout you would be able to have way more grip on your task behavior. Just like with any other task to give certain messages to your user or show fields yes or no based on what is in the rows. 

So it would be an opportunity to make things more versatile to enable more use of this great feature!


Jeroen van den Belt
Administrator
Forum|alt.badge.img+9
Needs feedbackOpen

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings