Hi All,
I am currently working on a project which is about to start designing my company's first installation of Livelink.
Although we are very soon to get the use of a resource from Open Text to help us through the first few projects in the programme, I would like to get some of you guys' and gals' opinions on Livelink's capabilities to deliver certain 'off-the-wall' requirements. I'm not necessarily looking for an in-depth 'how to', just an idea as to whether these things are achievable 'out-of-the-box' with a bit of configuration or whether they require a large development effort.
Well, here goes:
- Sending alerts from workflow triggers to distribution lists determined from the document in relation to the creator/data owner.
- Search through a node in the file plan and all subordinate nodes to determine which documents need to be recalled when cancelling a workflow process e.g. documents part way through thier lifecycle.
- Changing ownership of a hierarchy of documents.
- Collecting the organisation/team structures from the user profile?
- Can we inherit distribution lists from another document from another profile to both an alert and a document?
- Can we route folders?
- Real-time (yes real-time) withdrawal of access - system logs you off and the current document is closed. (yeah - I thought that too, but I might as well ask while I'm here!)
- Forms constrained by user profile e.g. configurable signoff for expenses payments according to role/profile. Also alters the workflow of the document.
- Reports against read receipts for informational notifications. Even is there such a concept of read receipts outside of the email application?
- Real-time pop-ups? (I know Livelink is 'pull' technology so I'm not hopeful with this.)
- Interruption of processes in real-time. e.g. stopping a search that is taking too long.
- What are the capabilities of the alerting/notification functions? Can you set alerts to be triggered on any object to any recipient? Can you set an alert to be triggered when a document is 'hit' during a search?
I appreciate that this is quite a long post (especially as its my first one here), and I don't expect anyone to address all the above points, but I'd be really grateful for a 'heads up' as to what sort of nightmares may lie ahead.
Cheers,
Seldom
P.S. Congrats on the forum - there seems to be a drought of Livelink resource out there on the Web (Mr. Griffiths you are a saint). I realise that this is how Open Text make a large amount of thier money, but I can't even find a single book on the subject!!
I am currently working on a project which is about to start designing my company's first installation of Livelink.
Although we are very soon to get the use of a resource from Open Text to help us through the first few projects in the programme, I would like to get some of you guys' and gals' opinions on Livelink's capabilities to deliver certain 'off-the-wall' requirements. I'm not necessarily looking for an in-depth 'how to', just an idea as to whether these things are achievable 'out-of-the-box' with a bit of configuration or whether they require a large development effort.
Well, here goes:
- Sending alerts from workflow triggers to distribution lists determined from the document in relation to the creator/data owner.
- Search through a node in the file plan and all subordinate nodes to determine which documents need to be recalled when cancelling a workflow process e.g. documents part way through thier lifecycle.
- Changing ownership of a hierarchy of documents.
- Collecting the organisation/team structures from the user profile?
- Can we inherit distribution lists from another document from another profile to both an alert and a document?
- Can we route folders?
- Real-time (yes real-time) withdrawal of access - system logs you off and the current document is closed. (yeah - I thought that too, but I might as well ask while I'm here!)
- Forms constrained by user profile e.g. configurable signoff for expenses payments according to role/profile. Also alters the workflow of the document.
- Reports against read receipts for informational notifications. Even is there such a concept of read receipts outside of the email application?
- Real-time pop-ups? (I know Livelink is 'pull' technology so I'm not hopeful with this.)
- Interruption of processes in real-time. e.g. stopping a search that is taking too long.
- What are the capabilities of the alerting/notification functions? Can you set alerts to be triggered on any object to any recipient? Can you set an alert to be triggered when a document is 'hit' during a search?
I appreciate that this is quite a long post (especially as its my first one here), and I don't expect anyone to address all the above points, but I'd be really grateful for a 'heads up' as to what sort of nightmares may lie ahead.
Cheers,
Seldom
P.S. Congrats on the forum - there seems to be a drought of Livelink resource out there on the Web (Mr. Griffiths you are a saint). I realise that this is how Open Text make a large amount of thier money, but I can't even find a single book on the subject!!