Just as a note
In the case of locking the job, BPM does not work as
well as a BAM
BPM works on the business objects and the problem is
that Job status maintenance, jobentry, etc are different business
objects.
Hence a BAM is the best place as it allows you to in
effect handle a write trigger
i.e. when a job is added to jobhead, make it locked.
One further clarification - BAM's are not reoccurring in
that they are scheduled tasks, they occur on writing to the table they
are in effect triggers
Customization has the issue that it needs to be
published and the different UI's need to be modified.
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Robert Brown
Sent: 15 April 2008 12:20
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Automatically Lock Jobs
(Now) on 404: I put a customization in place to lock qty (one of 1/2 a
dozen things the customization automates) every time a job is created or
loaded into job entry. The customization was created on 305i so you
should be able to do what you want.
You could also create a BAM (recurring every few minutes) to simply
punch in TRUE values to lock unlocked job qty's and schedules.
BPM would also likely work and, unlike customization, has the benefit of
doing what you want across multiple applications (that invoke the same
event trigger).
Use whatever tool you are best versed in.
"Rojas, Joe" <joe.rojas@...
<mailto:joe.rojas%40symmetrynb.com> > wrote:
Hello,
We are running 8.03.305K on Progress.
I'm trying to come up with a way to automatically lock the schedule and
production quantity of a job at the same time a user releases a job.
I was thinking I might use a BPM but I don't have much experience with
BPM. Maybe a customization?
Anyone have any suggestions?
Joe Rojas
Information Technology Manager
Symmetry Medical New Bedford
P: 508.998.4575
C:508.838.4717
joe.rojas@... <mailto:joe.rojas%40symmetrynb.com>
<mailto:joe.rojas@... <mailto:joe.rojas%40symmetrynb.com> >
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
In the case of locking the job, BPM does not work as
well as a BAM
BPM works on the business objects and the problem is
that Job status maintenance, jobentry, etc are different business
objects.
Hence a BAM is the best place as it allows you to in
effect handle a write trigger
i.e. when a job is added to jobhead, make it locked.
One further clarification - BAM's are not reoccurring in
that they are scheduled tasks, they occur on writing to the table they
are in effect triggers
Customization has the issue that it needs to be
published and the different UI's need to be modified.
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Robert Brown
Sent: 15 April 2008 12:20
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Automatically Lock Jobs
(Now) on 404: I put a customization in place to lock qty (one of 1/2 a
dozen things the customization automates) every time a job is created or
loaded into job entry. The customization was created on 305i so you
should be able to do what you want.
You could also create a BAM (recurring every few minutes) to simply
punch in TRUE values to lock unlocked job qty's and schedules.
BPM would also likely work and, unlike customization, has the benefit of
doing what you want across multiple applications (that invoke the same
event trigger).
Use whatever tool you are best versed in.
"Rojas, Joe" <joe.rojas@...
<mailto:joe.rojas%40symmetrynb.com> > wrote:
Hello,
We are running 8.03.305K on Progress.
I'm trying to come up with a way to automatically lock the schedule and
production quantity of a job at the same time a user releases a job.
I was thinking I might use a BPM but I don't have much experience with
BPM. Maybe a customization?
Anyone have any suggestions?
Joe Rojas
Information Technology Manager
Symmetry Medical New Bedford
P: 508.998.4575
C:508.838.4717
joe.rojas@... <mailto:joe.rojas%40symmetrynb.com>
<mailto:joe.rojas@... <mailto:joe.rojas%40symmetrynb.com> >
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]