Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi All,
We have an application inside stream with App owner as "A". Another User "B" took a duplicate of this app and made changes in script and replacing the existing app inside stream. App got replaced but after reloading the app inside stream changes are not reflecting.
Could you please help is any security rule issue.
Thanks
Anjali
Check that the app isn't in the midst of a reload while it is being replaced.
Otherwise, if things are different than expected after a reload, this can be a result of any number of things, but without knowing the specifics, it's hard to venture any sort of guess.
Check that the app isn't in the midst of a reload while it is being replaced. - No Checked
Im not able to replace other owner app
If you're not able to replace the app, then what does the reload have to do with it? A red herring...
This is normal. You would need to create a security rule to allow you to override other people's apps. I would advise against doing this. Instead, go to QMC and change the publish app's owner.
@Or / MVP, Let me explain in detail,
Stream Name: AAA,
Application Name: AA,
Owner: A
Took a Duplicate of a app from Stream where Owner A
and im making changes in my work stream and trying to replace this app. App got replaced (i can see the changes in UI is getting reflecting), but when i open a script coding is missing if i reload or if i take duplicate published changes wont get reflect.
Only this happening if i try to replace other owner app.
Does the same thing happen if you take ownership of the published app before republishing?
@Or , Does the same thing happen if you take ownership of the published app before republishing? - No, i can able to publish and can see the change
Then I would suggest you check your security rules that allow publishing over someone else's app. They may not include the required sub-objects such as script.
That said, I would recommend not allowing override of another person's app. I've found that the best approach is to require the person publishing to take ownership of the app before republishing, which prevents mistakes and misunderstandings.