I need to add a checkbox to Job Entry details. When engineered is checked, the checkbox becomes read only. What is the best method of preventing this so the checkbox is always active.
Hey @jtinsley welcome to the group!
I know this is not really an answer to what you asked, but what is your setting here on Company Config?
I have not tried App Studio customizations yet (I mean barely, but not really), so I want to leave room for the real possibility of some way to accomplish what you want without changing company settings.
Having said that, I wonder if changing that setting is enough to get you by?
The Prevent Changes checkbox is True, and I need that to remain. I need to have a checkbox that can be checked to trigger the engineered and released buttons to be read only. The goal is to be able to lock jobs and prevent changes during compliance reviews.
Thanks for your reply.
If I understand what you’re looking for correctly:
Look at Data Rules in App Studio. You can’t edit the default ones so you’d need to add your own, but there is one called DisableJobHeadJobEngineered that controls when that checkbox is read-only. You’d just add another rule for when the field you specify is true, the action would be to set the Engineered checkbox to disabled.
I wired this one up to the Mass Print checkbox just because it was already on the form, but this disables the Engineered checkbox if Mass Print is selected. You’d do the same for the Released checkbox.
2 Likes
Thanks Ryan for the information. The issue I am having is that I have created a UD field in the JobHeadUD table. I added a checkbox to the detail page in app studio, and bound the checkbox to the UD field I created. When a job is engineered the newly created checkbox the checkbox becomes read only like the rest of the fields. We have prevent changes turned on in the company configuration. I want to use the prevent changes read only functionality to lock jobs, and then have a checkbox to make engineered read only to prevent changes by the users. I have yet to find a way to keep my new checkbox active. Hope this makes sense.
Perhaps the answer is not in this screen at all. You might save yourself the heartache and just make an updatable dashboard for this power user to change the status of the field.
You could still display the status of the checkbox in your customization, but let the editing be done somewhere else.
I do like seeing people overcome these kind of problems, so I’m not saying give up. But if you ever get ready to cut your losses…
It doesn’t address the specific issue, but it seems you could use a BPM? Maybe a pre-process directive on update or the methods being called to prevent the activity
Depending on what you want to use the checkbox for there are a few built in ones that should work for what you are describing. Look at the fields jobHead.CheckOff1-5. These remain active when the job is engineered and released.
They are also searchable in the job status field in job search.
You can find them in Company configuration \ Modules \ Production
1 Like
That’s the answer!
Works great!
Thank you