Service Connect/Job Inconsistencies

I eventually discovered that what was happening was that my users were
running the workflow twice, which was causing Vantage to perfrom the
behavior described in my initial post.

While I agree that in this situation, the problem was caused by my
error, that doesn't change my complaints with Support on Service
Connect. All they really seem to know about Service Connect is how to
set it up and that's all, not even really what it is capable of, as
the support person flat out told me that the Labor Service couldn't be
used by Service Connect. It would be nice if they would at least be
able to tell me that they can't help with Service Connect usage issues
before the second or third time I called in.

Service Connect isn't a bad tool, it just doesn't work as smoothly as
I would wish it would. I don't think that it is straight-forward
enough that a non-programmer can easily use it, which is how it was
pitched to us. I probably would have been better off getting Visual
Studio.NET, and just directly calling the Web Services instead of
relying on the overhead of Service Connect.

RussN

--- In vantage@yahoogroups.com, "David" <dmclaughlin@...> wrote:
>
> doesn't sound like you are having any problems with service connect...
> It could be that you may be missing a particular webservice call
> somewhere in the transaction sequence...
>
> when you are mimicking a user transaction, you need to first turn
> tracing on, then manually do the transaction you wish to automate...
> (kind of like a macro recorder) Afterwards, you need to study the
> trace log for all calls that were made and determine if you are
> missing something.
>
> I think the support people will help you get service connect to
> successfully make a webservice call... but whether you are able to
> successfully automate a complicated user transaction is up to the
> developer, not support.
>
> --- In vantage@yahoogroups.com, "russnewcomer" <rnewcomer@> wrote:
> >...I am wondering what others do when they have struggles
> > with Service Connect? Did you teach yourself SC, or did you have
> > someone come onsite to help? I've contacted the consultant I've
> > worked with before, but am I going to have to pay a consultant for
> > support on this?
> >
>
I am having an issue with Service Connect, and Tech Support pretty
much told me that they couldn't help me, and recommended that I get a
hold of Consulting or Custom Programming. Tech Support first told me
that Service Connect would not do what I have it doing, and I'm not
entirely sure the folks I talked to had any prior experience with
Service Connect before, also because they started talking about how
they can do simple things, but can't help with complex BAQs or menu
buttons. I guess support can't help with service connect, but I wish
they would just say that up front, instead of bouncing me between
three people.

Anyway, here's the rundown on my problem:

We group parts together to run multiple jobs at a time in a certain
resource group. (this group is set up for Labor=Burden, this will be
important later) Clocking in and out of possibly 40 jobs in MES
is s--l--o--w, so I developed two Service Connect workflows, one to
clock a user into a jobs, and one to clock them out. The clocking in
has been going for a week or two, and works great. I just released
the clocking out workflow yesterday, and it seemed to be working fine.
Yesterday afternoon, I was informed that there were some records that
had inaccurate burden amounts.

As I said, we have Labor=Burden on the resource group, we also have
use estimates. So for example, I have two jobs nested together, job A
has an estimate of 1 hour, Job B has an estimate of 2 hours (total of
3 hours). When I run the jobs, I'm clocked in for 6 hours, so Job A
gets 2 hours of labor time allocated, Job B gets 4 hours of labor time
allocated. The resource group is setup for Labor=Burden, so there are
then 6 hours of total burden assigned, split 2 to job A, 4 to Job B.
This setup works, and is what we've been seeing out of MES clock
ins/out for the past 6 months, and Service Connect INs/MES outs for
the last two weeks.

Now, I'm seeing some the following behavior

If a user clocks in using the Service Connect Clock In workflow, then
clocks out using the Service Connect Clock Out workflow, Burden is
correct.
If a user clocks in using the Service Connect Clock In workflow, then
clocks out using MES, Burden is correct.
If a user clocks in using MES, then clocks out using MES, Burden is
correct.
If a user clocks in using MES, then clocks out using the Service Connect
Clock Out workflow, Burden is *SOMETIMES* the total time the user
spent clocked in. Also, *SOMETIMES* the Operation Complete flag will
be set on the Labor Transaction, but not in Job Completion/Closing,
and when the next operation is started, they get "The Previous
Operation has not been completed."

Obviously, the easy solution is to not do #4, and we're working to put
procedures in place to prevent that. My bigger concern is that it is
inconsistent, and therefore I'm missing something else in my workflow
that is going to have unknown repercussions down the road.

While I don't necessarily expect the group to solve my problem (but it
would be great if you could, zen-like, without seeing the code or
anything!), I am wondering what others do when they have struggles
with Service Connect? Did you teach yourself SC, or did you have
someone come onsite to help? I've contacted the consultant I've
worked with before, but am I going to have to pay a consultant for
support on this?
"Struggles" is a mild statement. We got a week of training then
promptly found we need much more.
With no documentation and limited call center help, Service Connect is
very hard for us also. We too have had occasions where we were told
it cannot be done, but we did the task.

We also have issues with things that work one way but not another.
Currently we have a daily SC run that sometimes works and sometimes
gives errors. A server reboot seems to help, but we still are
investigating.

By the way, if its been a while since training, chances are you will
need to pay for the consultant time.
Good luck,
djj
doesn't sound like you are having any problems with service connect...
It could be that you may be missing a particular webservice call
somewhere in the transaction sequence...

when you are mimicking a user transaction, you need to first turn
tracing on, then manually do the transaction you wish to automate...
(kind of like a macro recorder) Afterwards, you need to study the
trace log for all calls that were made and determine if you are
missing something.

I think the support people will help you get service connect to
successfully make a webservice call... but whether you are able to
successfully automate a complicated user transaction is up to the
developer, not support.

--- In vantage@yahoogroups.com, "russnewcomer" <rnewcomer@...> wrote:
>...I am wondering what others do when they have struggles
> with Service Connect? Did you teach yourself SC, or did you have
> someone come onsite to help? I've contacted the consultant I've
> worked with before, but am I going to have to pay a consultant for
> support on this?
>