This may be a bug, or it may just be the way the thing is designed:
One of the many parameters in the Security Policy module, in the ‘Policy Content’ tab, is ‘Document Content’, for which you have a choice of three:
Use Content (which means you type in the content in a dialog there on the screen)
Use URL, or
Use Attachment
It seems that once a document is created, you cannot change between these, it’s ‘stuck’ with the original type. (But you can ‘change’ it in the Security Policy Review objects… but that doesn’t work)
This tripped me up recently:
for our Docs process, colleagues will tell me the title of new documents they have, and I will allocate a reference number for it and create and entry in the Eramba Security Policy module. But because they haven’t written the actual document, I thought i would be clever and, instead of uploading a dummy Attachment of the doc, I just selected ‘Use Content’ and typed ‘Just a draft for now’ in there.
However, when they their doc was ready for realise, I went to the first ‘Security Policy Review’ object for the doc and there, the Document Content field is NOT locked / greyed out,
so I could change it to ‘Use Attachment’ and I attached the document.
But, the parent Security Policy object still has its Document Content property locked as ‘Use Content’,
and when my users go the Policy Portal, they released version of the document isn’t there to download when you click into its entry.
The fact that you can change this parameter in the Review object but not in its parent suggests to me that this is a bug, not a feature…?
I can’t see a reason why the parameter should be locked, as it’s perfectly reasonable for new editions of documents to change their delivery format.
i’m sorry i think i perhaps dont understand … is best if you describe a bug as steps that we can reproduce … for example this is what i tried to do based on your input:
1- create a policy, content type editor (content):
I think you are trying to do the same steps as me, yes.
But when you create a Security Policy, do you not find that its Document Content field becomes greyed out and can no longer be changed? (It can be changed in child Security Policy Reviews, but I found that what is shown in Policy Portal is then stuck that the content type set in the original Security Policy)
OK, that makes sense.
But in that case I definitely experience a bug in the portal:
I had completed the policy’s first review, and changed it there to ‘Use Attachment’,
but in the Policy Portal, it was just showing me the original ‘Use Content’ version.
I had to delete the Security Policy and make a replacement. (This means I can’t screenshot it for you to demonstrate it, because the misbehaving one is deleted, of course! )
I’m surprised that it didn’t reproduce for you.
It’s possible that what happened was that I somehow messed up the dates of my reviews, thus meaning that Eramba still regarded the v1 as the ‘current’ one…?
)