Hi There,

Trying hard to build a nice and complicated system for our work to book in job forms.

So far I have built a CCK node which grabs details like first name, phone number etc etc now the problem is I need a selection at the top of the node/add that asks "Is this an Existing User or a New User" so if the user is new their first and last name and phone number are assigned a UID. This way when they come back we can search their name and using the UID it can tell me all previous nodes assigned to that UID.

I can't use the standard Users module as this is needed by Tech / Sales staff for workflow management.

Any idea's?

Comments

Raf’s picture

Can't you make an extra role for these users and assign them to that, or do Tech / Sales staff need the entire user database to be without those users, and not with every user, some of which're marked with this role?

SamuelFreeman’s picture

Well that could be an option but can you sign up a user without email address and just with a first name, last name and phone number and no Username?

And also can a user be added from within a node / add page?

Raf’s picture

A user can be created programmatically using user_save(), so yeah, it's possible to add a user within a node / add page (or any other page).

Signing people up without an email address is something I don't know, sorry. Can test this myself, but I'm sure someone on these forums already has the answer to this, so I'll leave that up to them.

SamuelFreeman’s picture

Thanks Raf, great help, I'll have to look into that user_save()

no_idea_yet’s picture

Haven't had a chance to play with it but stumbled over osTicket the other day (http://osticket.com/). Looks like it has a good feature set that may fit your requirements; just embed it in a node.

Adam S’s picture

I don't understand why a person has to be a user object? Why can't the 'person' be a node with a name, address, phone number, ect.

1. have a job form that is a node with a node reference to a person node.
2. have a person node with a user reference to a user. This can be optional. So if you build it where the person can log in you can use a module (I forget the name) that will enable a person in a user reference to edit that node that their user object is being referenced by.
3. in Views use the argument of NID for the job and use the relationship of the 'person' node type. This will allow you to create a list of fields in the fields box that containes all the fields in the job node type and also in the 'person' node type

If you want an example of how this might work, download OpenPublish and look at how they set up the Author node types. It will take ten minutes.