# Why does ABB not support Custom Proc syspars? (Found a fix)

**URL:** <https://tech-community.robotics.abb.com/t/why-does-abb-not-support-custom-proc-syspars-found-a-fix/12030>\
**Category:** OmniCore\
**Created:** [September 17, 2025, 8:52am UTC](https://tech-community.robotics.abb.com/t/why-does-abb-not-support-custom-proc-syspars-found-a-fix/12030 "2025-09-17T08:52:03Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Markus\_Naslund](https://avatars.discourse-cdn.com/v4/letter/m/b9bd4f/32.png) [@Markus\_Naslund](https://tech-community.robotics.abb.com/u/Markus_Naslund)\
**Post date:** [September 17, 2025, 8:52am UTC](https://tech-community.robotics.abb.com/t/why-does-abb-not-support-custom-proc-syspars-found-a-fix/12030/1 "2025-09-17T08:52:03Z")

</div>

Does anyone know the reason why ABB removed the possibility to create customized system parameters in a RobotWare add-in for Omnicore?

The possibility to use the invoke command in the install script is removed in Omnicore and it seems to be needed to make use of customized system parameters.

Edit: Invoke is not needed, It seems to be working when directly calling cfg\_create\_type\_from\_rules\_def. (works on VC, not tested on RC)