Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 7346 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies
Posted

I have a multi-user helpdesk and I would like to develop a drop box where each of the users can pull their own name down and that would initiate the script that sorts the jobs and presents the job list. I have been able to create the scripts that get the proper layout/report to show.

How do I link the selection field to say "If (staff select) = "Nate" then run script1

TIA.

Posted

You would do it within the main script.

If [staff select = "Nate"]

Perform Script [script 1]

Else If [staff select = "Sheila"]

Perform Script [script 2]

.

.

.

End If

End If

Posted

But what is different about the scripts? Why not run the very same script in all cases but write that script to go to the correct records for the user? Or maybe, why have a script at all? Why not just a filtered portal?

Posted

So the one script would contain code like:

Go to Layout ( by calculation:

Let ( [ n = Get ( AccountName )] ;

Case ( n = "Nate" ) ; layout1 ;

n = "Nancy" ); layout2 ;

.

.

)

)

Posted

Since Staff always come and go, I think I would include a script number field in your staff database and join them. In this way, several staff can even share the same script to run, depending upon their name (for the find) and allowing for different scripts according to other criteria as well. It would eliminate hard-coding the staff name within the scripts themselves. Yes, many ways to go here. I wouldn't want to modify the script every time a staff person came and went. frown.gif

I perform finds all the time by freezing window, switching to correct table occurence and then, depending upon your setup, Enter Find [], Insert Calculated Result [... insert many new Get() functions here ... ]

You can turn this into a generic, simplified process which eliminates hard-coding entirely. Vs. 7's ability to Get(AccountName), Get(ActiveFieldContents), and Get(ScriptParameter) could pretty-much handle it all for you. wink.gif

In fact, why would they even need to select themselves from a popup? One click of one button could run according to who they were.

LaRetta

  • Newbies
Posted

Interesting. We are using one interface for multiple users, and on top of that, one user (like me) may pull the constrained sort (currently the If .. Else If scripts) and then print the .pdf of open/pending records to email to them. In this case, the user often never even accesses the database.

>>what is different about the scripts? Why not run the very same script in all cases but write that script >>to go to the correct records for the user? Or maybe, why have a script at all? Why not just a filtered >>portal?

Ideally, I would like the script to run the constrained find for whatever username was in the box, which we put into the "staff" value list anyways. Currently, there is the pull-down field to select the name, and then a magnifying glass icon to perform the If..Else If with an If for each staff that needs this kind of job list.

And then the pull-down box changes it's display value ... almost randomly! i.e., when I select "Nate" and press the m-glass, the sort works perfectly and then the value of the box will change to someone else on the list like "Jackie". This doesn't happen the same for everyone although sometimes it's the next name down the list or the next three.

  • Newbies
Posted

I had inserted a normal field with a value list associated. It was not global storage. Now that we have enacted global storage the name in the search field remains after performing the script. Thanks. I'll start a new post if there are anymore issues concerning this.

This topic is 7346 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.