go to post Ben Spead · Sep 8, 2023 @John Murray - I was just informed that the cloud team is aware of the issue and they plan to push a fix this AM. No need to contact Support on this one :)
go to post Ben Spead · Sep 8, 2023 John - FYI ... you can reach out to Support to help with issues like this. Sounds to me like a bug that they we would want to jump on quickly. Thank you for bringing it to our attention!!
go to post Ben Spead · Sep 7, 2023 Thank you for all of your hard work ... it's amazing to see how far this ecosystem has come in the past couple of years :)
go to post Ben Spead · Aug 29, 2023 Ahh ... if they need to be used elsewhere then that is a different story. I forget off the top of my head exactly how this would work, but you could potentially subclass your Org class and just add the parent cardinality relationship. I *think* that should force the extent of the subclass to be embedded in the parent class ( @Dan Pasco?), which should automate the cascading delete for you without impacting the Orgs stored independently.
go to post Ben Spead · Aug 28, 2023 Thank you @Bernd Mueller - can you point me to which types of things would necessitate the restart of the hosting webserver?
go to post Ben Spead · Aug 28, 2023 Thanks chad - scripting automatic review failure is more involved than just scripting the calling of the API at deployment time (and not relying on RELOAD=1) so we'd probably go that route. If RELOAD = null is hardcoded for immediate removal than probably relying on that would be the more risky approach to change control in this case. So we'd likely rely on "Set status = %CSP.Mgr.GatewayMgr.ActivateCSPIni()" for automation.
go to post Ben Spead · Aug 28, 2023 @Dan Pasco - anytime I see you respond to a D.C. question I always take the time to read it carefully as I know I will definitely learn something (and this response did not disappoint!) Quick question - what is the use of $$$QN() as I can't find it in the docs? I think you should consider publishing this as a standalone article.
go to post Ben Spead · Aug 24, 2023 thank you for the excellent summary! I recommend that you create a standalone article highlighting what you have learned.
go to post Ben Spead · Aug 24, 2023 @Hannah Sullivan ... does Organizations have to be a list? If it is a Parent/Child relationship then I believe the children are stored by default in the extent of the parent so deletion of the parent automatically deletes the children.
go to post Ben Spead · Aug 24, 2023 Thanks for the great work on this @Evan Gabhart and @Matthew Giesmann! This should be very helpful for keeping environments clean!
go to post Ben Spead · Aug 23, 2023 Thanks @Bernd Mueller ... this is very helpful! Do you see an issue with having RELOAD = 1 always in source control, even if it is removed from the environment copy? I really like the idea of it reloading, but am concerned about RELOAD = 1 being removed from the copy sitting on our DEV environment where all changes originate ... it would be too easy for someone to accidentally upload a new version of the file without RELOAD = 1 being in the file, meaning it would propagate through our CICD pipeline without that value present and not automatically be activated in higher level environments. Do you know if there is a way to prevent RELOAD = 1 from being removed from the CSP.ini?
go to post Ben Spead · Aug 15, 2023 Please note - I updated the article to highlight the new Usage Warnings in the Overview tab (nice work @Alexander Obolenskiy!) Please provide feedback as to whether this is useful and how it could be more helpful!
go to post Ben Spead · Aug 14, 2023 Great course! I strongly recommend it for any Tier 1 sites using CCR if you haven't taken the training yet :)
go to post Ben Spead · Aug 14, 2023 The issue is that you need the logic to run synchronously in process so that it can actually write out the JavaScript as part of the response to the web client. If you job off the logic it will run in a separate process and there is no way to return the JavaScript to the caller because this is done asynchronously and the response has already been sent by the time your job will finish in all likelihood. If you need something to run asynchronously then use the #call() command in your CSP page.
