Need a little instructions on how to apply a rule

[Rayed]

That is a good idea LeberMac. I will try it and let you know. I am working on a Mac.
Rayed

[Rayed]

Well, I changed the Date/Time on my Mac to 2010, but the online pdf proof Disclaimer still said 2009.

So now I am wondering, is the pdf proof and hi-res proofs generated online use an internal Printable Date and Time that the rule:
"return FormatDate(Today(), "yyyy");" could be picking up?

Or does that rule pick up the date and time from what ever computer initiates the download?

I just think that my rule is not correct and is not applying the year correctly.
Rayed

[LeberMac]

Hrm. I dunno. I defer to Sweet and Dan on this one.
I'm unsure as to where FusionPro picks up its date & time data.

Stupid question that I forgot to ask - you are using FusionPro Desktop, right? (Cause if it's being composed somewhere else, you'll need to change the date/time there. Forgive me if that seems like the condescending "Is your computer plugged in?" tech support question.)

[Rayed]

Yes, I am using FusionPro Desktop on my Mac which is plugged in. But I think it is my rule. I don't think I did it right.
Thanks for your suggestions, however.

I suppose if Dan or David took a look at my rule, they could tell me if I applied it correctly.
One question I had for Dan, which could be obvious is, what exact rule information goes into the "rule_Copyright" rule. I assumed it was this:
"return FormatDate(Today(), "yyyy");" but he did not specify.
Thanks,
Rayed

[Dan Korn]

Originally Posted by Rayed

Well, I changed the Date/Time on my Mac to 2010, but the online pdf proof Disclaimer still said 2009.

So now I am wondering, is the pdf proof and hi-res proofs generated online use an internal Printable Date and Time that the rule:
"return FormatDate(Today(), "yyyy");" could be picking up?

Or does that rule pick up the date and time from what ever computer initiates the download?

I just think that my rule is not correct and is not applying the year correctly.
Rayed

The Today() function returns a JavaScript Date object representing the current system date and time, on the machine where the function is called. At composition time, it returns the system date and time on the machine where the composition is performed. So, if you're composing on a remote FP Server machine, which is what happens when you submit a job to FP Web, then the composition picks up the date and time from that remote composition machine. Changing the system clock on your local machine will only affect compositions preformed locally on that machine; it can't possibly have any effect on a composition which occurs on a different machine.

Obviously the composition machines running jobs for FP Web are set up with the actual current date and time. I would expect that these machines are set for Pacific Time, since we're a California-based company.

Originally Posted by LeberMac

Hrm. I dunno. I defer to Sweet and Dan on this one.
I'm unsure as to where FusionPro picks up its date & time data.

Stupid question that I forgot to ask - you are using FusionPro Desktop, right? (Cause if it's being composed somewhere else, you'll need to change the date/time there. Forgive me if that seems like the condescending "Is your computer plugged in?" tech support question.)

Well, no, actually, it's not a stupid question at all. In fact, it's exactly the right question to ask. The context under which you are running a job is absolutely relevant and crucial to diagnosing any issues. See my signature.

Originally Posted by Rayed

Yes, I am using FusionPro Desktop on my Mac which is plugged in. But I think it is my rule. I don't think I did it right.
Thanks for your suggestions, however.

I suppose if Dan or David took a look at my rule, they could tell me if I applied it correctly.
One question I had for Dan, which could be obvious is, what exact rule information goes into the "rule_Copyright" rule. I assumed it was this:
"return FormatDate(Today(), "yyyy");" but he did not specify.
Thanks,
Rayed

Like I said earlier, you can use the Today() function, and it is guaranteed to return the current date and time, on the machine where the composition is being performed. I'm not sure why my assurances in this regard aren't satisfying, but you also now have empirical results that back this up: specifically, you saw that changing the system time on your local machine affects the date returned for a local composition, but not for a remote composition (via FP Web).

And as I also noted earlier, instead of always using the "current" date at the time of composition, you might want to hard-code a specific year into that function, in case you happen to be composing a job which is intended for printing or mailing at a later date than when the composition is performed. But you did not seem interested in this advice either.

In the end, exactly what logic should go into your rules depends on your business requirements, and I can't tell you what those are.