7.1 Extranet Architecture
Firstly, you need to understand how the Extranet system operates. We’ll explain quickly here, but you should refer to the Tribiq CMS User Manual for detailed understanding.
Your Tribiq CMS website has one Extranet. However, you can have multiple entry points to the Extranet - we call these Extranet Content Items. Each Extranet Content Item is assigned a Signup Model.
It's like an entry system to a theme park - you can join the single queue, family queue, the elderly queue or the childrens queue. Once in these queues, you can purchase a day-ticket, a week-ticket or a season pass. Your Tribiq CMS website can provide multiple queues (Extranet Content Types) with mutliple ticket types (Signup Models), to the same theme park (the Extranet).
Tribiq CMS allows you to have a number of “Extranet Signup Models”. You might want to process an extranet registration differently for different types of users. You might create a “Partner” signup model, a “Client” signup model, or a “Alumni” signup model, for example. Each model can request different registration information, take the visitor through a different amount of “steps” or “stages”, or have different methods of validation.
A signup model is associated with a Extranet content item. A signup model is not associated with a template. This means that you can create just one Extranet template if you want to use multiple models.However, if you want them to use different template designs, then you should probably create another template.
If you want specific users to signup with specific signup models, you must direct them to the appropriate content item. You will note that throughout both extranet templates and extranet includes (such as a login form), by default we send people to and from the following URL:
/?cID=1&cType=extranet
However, if you have created multiple Extranet Content Items, for different Signup models, you will need to change this throughout your templates depending on the Content Item that uses the model you want the user to use, linking to the correct cID.
For example, you might assoicate signupmodelX with the first extranet page you create (e.g. /?cID=1&cType=extranet), and you might associate signupmodelY with another extranet page (e.g. /?cID=2&cType=extranet)
This may be important in redirecting your users around the website.
Top of Page