![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Broadcast Message using DXL Topic Summary: How to send a message to a user using a DXL script? Created On: 15-Feb-2008 06:07 Status: Post and Reply |
Linear : Threading : Single : Branch |
|
![]() |
![]()
|
![]() |
|
Hello Experts,
There is a new feature in DOORS 8.2 to broadcast/send a message to a user in the network if he/she has an exclusive edit lock for a module. Could anyone let me know how do I achieve sending a message to a network user who is logged in using a DXL script? This part is not covered in the DXL help Library. Thanks in advance, Regards Irfaan |
|
![]() |
|
![]() |
|
I'm not sure you can send a message to a particular user. Would be great if you could, you can send a broadcast message, which sends the message to everyone using string sendBroadcastMessage(string). Granted I haven't tried this yet due I'm our evaluation license for 8.3 has expired.
I would be interested to know if there is a way to send a message to a specific user as well. It could come in very handy. ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
|
![]() |
|
Well there has to be some functionality to send a message to a single user since in DOORS 8.2/8.3, when you try to open a module in exclusive edit and someone else has it locked, you can send them a dialog saying you want a lock.
------------------------- David Pechacek AAI Services Textron dpechacek@sc-aaicorp.com David.Pechacek@gmail.com |
|
![]() |
|
![]() |
|
I totaly agree with you David, I just haven't been able to figure it out yet. I wonder if the sendBroadcastMessage () could be overloaded with a user like:
string sendBroadcastMessage (string, User). Don't have a valid license to try it, but I didn't see in the Command Database for 8.2 that was posted on these forums awhile back. Here's the perms that I could find dealing with messaging: I'm guessing the Reply ones have something to do with the messaging as once you send a message (via lock request) you can send messages back and forth. string setReplyMessage_(string) string getIncomingReplyBody_(void) getIncomingReplyBody string getIncomingReplyHeader_(void) getIncomingReplyHeader void setReplyUI_(int replyUI(void)) string sendBroadcastMessage(string) SendBroadcastMessage There may be more that I missed. ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com Edited: 15-Feb-2008 at 18:03 by Scott Boisvert |
|
![]() |
|
![]() |
|
I tried a few variations of sendBroadcastMessage and none worked.
------------------------- David Pechacek AAI Services Textron dpechacek@sc-aaicorp.com David.Pechacek@gmail.com |
|
![]() |
|
![]() |
|
If you're running DOORS under a Windows environment, this may be useful.
Of course, it works only for users working in the same "Domain", and if your system administrator didn't disable the "net send" function... which is the case here but not where I worked before. ------------------------- E. Piallat CeBeNetwork |
|
![]() |
|
![]() |
|
I tried implementing something like that a while back, until I realized our IT dept. had disabled the "net send" function.
------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
|
![]() |
|
Hmmm... Net Send is not the right way to achieve this.
I guess as Scott hinted out, sendBroadcastMessage is the one which would actually serve the purpose. The problem is that this API sends message to all users. There is no API documented by Telelogic in the DXL help manual which sends message to a particular user. If anyone knows it, please let me know. Thanks & Regards Irfaan |
|
![]() |
|
![]() |
|
There must be a way, seeing when you send a request for a locked module to a particular user it only sends the message to that particular user. Has anyone entered a support ticket, I've ocassionaly found that I can get them to give me some undocumented functions
![]() ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
|
![]() |
|
I have done that... I havent got any reply from them :-)
|
|
![]() |
|
![]() |
|
I have a guy I can email.
------------------------- David Pechacek AAI Services Textron dpechacek@sc-aaicorp.com David.Pechacek@gmail.com |
|
![]() |
|
![]() |
|
Heh...I just sent in a support ticket as well.
------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
|
![]() |
|
The following does what you are asking, but there are limitations because we are using a perm for an unintended purpose.
------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
Very nice Tony, one more limitation is that if the module that is locked is locked shareable and there are other users with a shareable lock on that module, they all get the message.
Found this, cause my first thought was to have a DXL script open an empty module in shareable edit during client startup. Opened DOORS with 3 users sent a message to one user, and the two that had the share lock got the message. ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
|
![]() |
|
Damn it - better be careful what message you send then!
What about having an empty module per user that gets automatically opened in the background at client startup? ------------------------- Tony Goodman http://www.smartdxl.com Edited: 26-Feb-2008 at 14:58 by Tony Goodman |
|
![]() |
|
![]() |
|
Thats a lot of blank modules. ------------------------- David Pechacek AAI Services Textron dpechacek@sc-aaicorp.com David.Pechacek@gmail.com |
|
![]() |
|
![]() |
|
Thats a lot of blank modules. *LoL*.... I had thought of that, then I came to the same conclusion as David. For me, that could possibly be an issue as well, I have a few scripts that close all modules or all module but the current. This of course would have affected my first idea of a shared module as well.....Don't get me wrong what you have is great, but there has got to be something in either: C:\Program Files\Telelogic\DOORS_8.3\lib\dxl\standard\broadcasting\broadcastMsg.inc or C:\Program Files\Telelogic\DOORS_8.3\lib\dxl\standard\lockRequest\ That sends the message, without depenency on an locked module...If only we could unencrypt....*lol*. ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com Edited: 26-Feb-2008 at 17:54 by Scott Boisvert |
|
![]() |
|
![]() |
|
Hi David,
Can U mail to your contact and get the perm please? Thanks & Regards Irfaan Edited: 27-Feb-2008 at 04:52 by Irfaan Jamal |
|
![]() |
|
![]() |
|
Hi
We can use requestLock to send a message in case of locks on modules. I want to send a message even if there is a lock on Folders. The information of who has a lock I get from the manage locks. The information about the user is also available there. But sending a message is the issue. Regards Irfaan |
|
![]() |
|
![]() |
|
Hopefully David can get a better response from his contact than I did. My response from Telelogic support was:
"I have confirmed that currenlty this is not possible. But we can certainly submit as an Enhancement Request on your behalf to our Product Management to implement in future release." I highly doubt that it is "not possible", my opinion is that they don't want to release the method/function calls that allow this, or the guy has no clue as to what we are talking about. ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com Edited: 27-Feb-2008 at 15:41 by Scott Boisvert |
|
![]() |
|
Telelogic DOORS
» DXL Exchange
»
Broadcast Message using DXL
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.