Exposed Objects and CI/CD Piplines

[jessiebrooks]

I've written a couple of batch scripts to Generate a release from a given Package in one BP environment,  Import that release into the Next environment and then archive the .bprelease file.     

What I'm noticing is on occasion objects that were exposed for interaction with Webservices are no longer exposed.   Is this an artifact of the import process?   Is there a way to make sure objects that are exposed remain exposed?

------------------------------
Jessie Brooks
------------------------------

[david.l.morris]

How many times has this happened? Can you reproduce that issue?

I think it'd be worth looking at the XML of the incoming object and see if there's something different about those occasions. Off the top of my head, sometimes I wonder if having or not having a preferredid affects things like that. Also there was that issue with BP 6.5 where incoming processes wouldn't retain their being regularly published (not as web services). So maybe this is tied to that issue?

------------------------------
Dave Morris
3Ci @ Southern Company
Atlanta, GA
------------------------------

[jessiebrooks]

Thanks for the Reply.  It's really not consistent.  During testing of the release process I didn't really notice this issue.    We are using the Appian Skill to kick off a process in Blue Prism in response to a user work flow.   During a couple of the sessions we realized that Blue Prism was not responding to the Webservice call from Appian.   After bit of troubleshooting we noticed the business object Appian would use was no longer exposed.     It's happened a couple of different times but we didn't notice it at all until I started scripting the release process.    

We are on version 6.5 so that may be a factor as well.   I'll see if we can narrow it down to a particular release and check the xml.     Thanks!

------------------------------
Jessie Brooks
------------------------------