Jump to content
Salesforce and other SMB Solutions are coming soon. ×

IWP and FM 10


Jim_Shelton
 Share

Recommended Posts

Can I create a link that will enable an outside user to access a single record via IWP. I believe this was not possible in 9.

 

thanks,

 

Jim

Link to comment
Share on other sites

Can I create a link that will enable an outside user to access a single record via IWP. I believe this was not possible in 9.

 

What is the conditional situation for a given user to see a given record? There are a lot of solutions, but some more information is needed. IWP may not be the restriction in this, but at this point, I can't tell.

Link to comment
Share on other sites

Customer needs to view the proof of a specific job and only that job. A single customer could have only one job or hundreds. Do not want customer to see proofs of other customers.

 

My thought would be to have the link to the record of that specific job. Viewing this way the user can interact with questions on the proof.

 

Does this help?

 

Jim

Link to comment
Share on other sites

Customer needs to view the proof of a specific job and only that job. A single customer could have only one job or hundreds. Do not want customer to see proofs of other customers.

 

My thought would be to have the link to the record of that specific job. Viewing this way the user can interact with questions on the proof.

 

Does this help?

 

Jim

 

The first thing, however, would be to identify a record against a client. Does the client create it? If so, you can auto-enter the login ID in a field. If not, you need to manually enter the client name into a field in their records.

 

Given that, there are quite a few solutions.

 

One of the most obscure, but easy to implement, is in Accounts and Priviledges, for the privilege set for your clients,

 

in EDIT PRIVILEGE SET

the section entitled DATA ACCESS AND DESIGN

RECORDS popup menu, pick CUSTOM

 

The dialog that come up, lists all the TABLES in the db. You pick a table, then the popups at the bottom are where you put the LIMITED selection.

 

FM then throws up a standard calculation dialog box. This calculation is always used for this privilege set, regardless of who is logged in that has that privilege set.

 

The calculation is in the calculation dialog for the table in the privileges edit section ....

 

In the VIEW drop down, pick limited.

The heading about the calc entry field, will state

"Records can be viewed when:"

If (CustomerName = gPrivilegeSetName)

 

That's it - now customer records can only be edited, if the field contains the customer name where the privilege set equals the customer name.

 

You could, instead of Get (PrivilegeSetName) to set the varible gPrivilegeSetName, which requires a duplicated privilege set for each customer, do this based on global gAccountname using Get (AccountName) to populate this on login.

 

The reason for the setting a global at login, is that the GET function does not work within the privilege calculation dialog, as nothing triggers the action.

Link to comment
Share on other sites

But how is that getting to a generated link that goes to a specific record?

 

The record is not client created, only client modified.

 

thanks,

 

Jim

Link to comment
Share on other sites

The LINK can't do it.

 

A run-on-open script can do it. But in order to do it, it needs to be able to "know" who this person IS (so they have to LOG IN) and then it has to "know", given who this person is, what record or records ought that person to be taken to?

Link to comment
Share on other sites

You're going to create a record that has a field that contains the company name, say COMPANY1

 

A login for a customer from company1 has been created. Let's say the login name is COMPANY1.

 

You create a script that goes to a list view that is created with a FIND, where Get (AccountName) = companynamefield is the FIND criteria

 

The list then only contains records that are for this customer.

 

That is as tough/simple as it needs to be, however, this is not a very secure setup, as any mistake in code, or a menu choice left available, could open access to another customer's record.

 

The Accounts & Privileges approach is very secure, and should be used in conjunction with the basic navigation stuff above.

Link to comment
Share on other sites

This thread is quite old. Please start a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share



×
×
  • Create New...

Important Information

Terms of Use