It would be great if CA would publish Spel Code documentation or at least some examples for most common methods.
You can find some information on Spel Reference Guide - SDU
Yes i know, but there is a lot of missing pieces, a lot of methods that are not described or even not defined.
No, you can not. SDU was "retired". RIP.
If you have another source it will be great.
Gutis has done a good work cataloging Spel Code and he is a hero for me and my team, but without official documentation the puzzle remains incomplete.
SDU is back up and running.
SPEL API: BOP Manual Chapters by daniel-bighelini
I'm writing a digital book about Spel. When you're ready, I'll let everyone know.
The best source of this information is through the Community. TMACUL has done a wonderful job in this post Where can I find Spel functions documentation? to help you get to the information you need. We advise you to be cautious in adding SPL to your implementation as most of these customizations will not be supported.
Unfortunately, CA vendor has not yet understood that all its customers customize the SDM tool to meet their business needs.I agree that customizations should be made with care because they are not supported by CA support, but I point out that the vast majority of users who want to implement them are experienced users often linked to CA's accredited companies and it is absurd to imagine that these people have no official CA support documentation on the Spel language.Until when will this happen? Is the only way out is to wait patiently for the initiative of good faith people scattered around the world?Would not it be easier for CA to share this official knowledge about the Spel language with accredited companies?Could it be that the customizations implanted in the clients would not be made in a more professional way?It's a shame that CA does not see it that way.
Well said Daniel,
CarolPiccus, can you please re-consider this idea? Having official spel documentation available would be a huge asset to the community.
To Our Community Members:
We understand that our customers need to be able to make customizations to our solution. Therefore, our plan going forward is to invest in new ways for our customers to be able to adapt the solution to meet business requirements through configuration rather than customization. Our first goal is to provide a method that is easy to use, easy to support, and easy to upgrade. As for our legacy customization capabilities, we would like to propose that we partner with the community on the community documentation that has been started by validating the entries and providing additional information as needed.
Retrieving data ...