When we schedule a job from job entry the Schedule Job window pops up. We would like the “finite capacity” box pre selected. When we right-click and save layout, it never stays checked. Is there another way to save this as a default?
If E10, you could try a form customization
the right-click is the correct way to do this. If it doesn’t work, that is not normal, but since this is the old UI, i doubt that turning it in as a bug will get fixed.
One option is to do a trace just before you launch this. It might be possible to associate a BPM to automatically populate fields for you on that business object.
I was thinking a BPM, but my trace didn’t land on any method with a temp table to set this field to TRUE.
The form customization is also a possibility, but the example on the link threw a “Too many characters in character literal” error when I copied and pasted… trying to understand what would cause that.
Thanks.
A customization seems to work for me. We don’t really use the Finite Schedule (yet) so I can’t say if it really works.
In the job schedule customization, from the wizard, add an EpiViewNotification form event for the ScheduleEngine view. Once you do that, in the code generated, change the NotifyType to NotifyType.Initialize and add the line of code as below:
private void edvScheduleEngine_EpiViewNotification(EpiDataView view, EpiNotifyArgs args)
{
// ** Argument Properties and Uses **
// view.dataView[args.Row]["FieldName"]
// args.Row, args.Column, args.Sender, args.NotifyType
// NotifyType.Initialize, NotifyType.AddRow, NotifyType.DeleteRow, NotifyType.InitLastView, NotifyType.InitAndResetTreeNodes
if ((args.NotifyType == EpiTransaction.NotifyType.Initialize))
{
if ((args.Row > -1))
{
view.dataView[args.Row]["Finite"] = true;
}
}
}
That’s it. Again, you need to test this but I can definitely see the checkbox checked in the form.
Another thing, you need to have the same customization names for job entry and the job schedule forms. This is how you tell Epicor to use the customization you made for the job schedule form.
Dragos,
Thank you! What a clear explanation and the example worked on the first try. Thank you, again.
Actually, the users cannot “uncheck” the box now. They want it to default to checked, but also want the ability to uncheck it. Is there something I can change in this code to make that available?
Thank you.
You’re right. That’s because, as soon as you uncheck the option, the EpiViewNotification event fires again and checks it back. Forget about the EpiViewNotification event, the one below for the Form Load seems to work and it does let me uncheck it.
private void ScheduleForm_Load(object sender, EventArgs args)
{
// Add Event Handler Code
EpiDataView vSE = (EpiDataView)oTrans.EpiDataViews["ScheduleEngine"];
DataRow currRow = vSE.CurrentDataRow;
if (currRow!=null)
{
currRow["Finite"] = true;
}
}
Make sure you schedule a few jobs in your test/pilot and check if the finite schedule actually works.
Used this for the job scheduling form, as well as auto-checking the “Operation Standards” on the Job Traveler printing report. Thanks for the help!