Form Read Only

JordanMaxim

Hi,

Firstly I apologise if this has already been covered, I have searched the forum and couldn't find an answer.

I am calling a form from a process and I want the form to be read only.
-I have tried creating a rule on the BO:
Protect [BO] from All

-I have tried setting the BO to Read Only under the Access Levels, per this youtube video: https://www.youtube.com/watch?v=QivjkJNJ0Io&app=desktop

-I have also tried adding NO EDIT to the end of my process call, per this forum post:
How to set a form which read only (comment)&hilit=protect+form#p43744

Nothing seems to be working.
Ultimately I am wanting to stop the user editing the record and stop the Save message from popping up when you leave the record.

I am testing just as the Administrator.

Thanks for your help in advance.
Kind Regards

Jordan

customaware

Are you using VIEW or EDIT?

BLOMASKY

I thought NO EDIT at the end of the VIEW command worked really well. i.e. VIEW BO using "Bruces Form" NOEDIT

Bruce

JordanMaxim

eagles9999 wrote
Are you using VIEW or EDIT?

In my process I am using VIEW.
My process is:

VIEW [BO] USING [FormName]

JordanMaxim

BLOMASKY wrote
I thought NO EDIT at the end of the VIEW command worked really well. i.e. VIEW BO using "Bruces Form" NOEDIT

Bruce

Hi Bruce,
I had it as NO EDIT not NOEDIT so thanks for the clarification.
Unfortunately NOEDIT doesn't work the save message still pops up when you try to leave the record.
Thanks
Jordan

PointsWell

I thought I had developed the same problem.

However...

I found that I was opening a old record after I had added a new attribute that was a yes/no field.

The record loads but has no prior value for the yes/no field, then evaluates it to be no instead of null and then AIM determines that a change has been made and prompts for you to save the record. This does not show up on the logger as it doesn't appear to have a differentiation of null versus a no that just happens to not have been declared yet.

Create an AuditRecord BO with description as an attribute, then add the following rule to your BO.

IF MyObject WAS CHANGED THEN CREATE AuditRecord WITH
AuditRecord.Description=GET_CHANGES(MyObject)

MyObject is obviously the object that you have been trying to view.

This will immediately show you what AIM thinks it is updating.

You will obviously have to say Yes when you are asked "Do You Want To Save?", otherwise there won't be a change made

BenHayat

PointsWell wrote
I thought I had developed the same problem.

However...

I found that I was opening a old record after I had added a new attribute that was a yes/no field.

The record loads but has no prior value for the yes/no field, then evaluates it to be no instead of null and then AIM determines that a change has been made and prompts for you to save the record. This does not show up on the logger as it doesn't appear to have a differentiation of null versus a no that just happens to not have been declared yet.

Create an AuditRecord BO with description as an attribute, then add the following rule to your BO.

IF MyObject WAS CHANGED THEN CREATE AuditRecord WITH
AuditRecord.Description=GET_CHANGES(MyObject)

MyObject is obviously the object that you have been trying to view.

This will immediately show you what AIM thinks it is updating.

You will obviously have to say Yes when you are asked "Do You Want To Save?", otherwise there won't be a change made

Good point!