We created a power automate flow (using "for a selected message"), any message posted to the channel, we click "three dots" and click "more actions" then "See more" to select name of the power automate flow and execute accordingly. This doesnt sound to be user friendly.
Is there any way we can "pin" the name of the flow to somewhere nearest for example under chat section on the bottom of the screen ? So that it becomes more user friendly.
For more visibility, posting the answer from comment section:
The functionality you are trying to implement doesn't seem to be feasible at the moment.
Related
I am making a custom visualisation for Spotfire and I would like to store some state so the next time my visualisation is opened it can look the same. It is likely to be a small string. Is there a recommended way of doing this?
Thanks in advance
Chris
You can use a bookmark to store the "state" of your current analysis. You can add as many of these as you want, and name them whatever you want, and make them available to other users too!
https://docs.tibco.com/pub/spotfire/7.0.1/doc/html/bm/bm_how_to_use_bookmarks.htm
EDIT
Also, if you go to Edit > Document Properties > Library (tab) and check the "Remember personalized view for each Web Player user" this will save the last state of the analytic for each user, so when you open it back up it will look the way it did when you left it.
I have a script which makes users choose from different options in a list. I want there to be three buttons; OK, Cancel and Help (display a dialog with guidance).
However, it seems that I cannot use the "buttons" parameter within a list.
So how do I add additional buttons? (with a custom name, that displays a dialogue)
Current script:
set MyList to {"A", "B", "C"}
set Chosen to
(choose from list MyList with title "Connect to"
with prompt "What do you want to connect to?"
OK button name "Connect" cancel button name "Abort" ---and help
with multiple selections allowed) as text
Unfortunately choose from list supports only two buttons.
Alternatives are a (second) standard dialog which opens the list dialog or an AppleScriptObjC app with a custom dialog window.
While choose from list only supports two buttons, you can use AppleScriptObjC to create very rich alerts/dialogs. I recommend starting with Shane Stanley's free Myriad Tables Lib. Here's an example:
To learn more, read Chapter 26:Richer Interfaces of Shane's excellent $15 book Everyday AppleScriptObjC, available here. You could also look at Dialog Toolkit on the same page. Because Cocoa alerts and dialogs provide an "accessory view", you can put many additional controls in there.
I have Created a Notes Survey form using Lotus Notes Designer.
I select "Preview in Notes" and from there i forward the survey form to end user.
However this goes as an email and End user's has to Click on reply button to select their answers and then reply.
I am looking for some Notes Script / Commands which i can embed in a Notes button on the form, which will help end user to select the answer and once done, the reply should automatically mailed back to us.
Please let me know if additional information required, related to requirement.
Note: I am new to Notes Designer, and unable to club multiple options to get this working.
This is NOT the sense of a Lotus Notes application to send the information via mail. The most you do is, to send a button with the Command #Command([Compose]; "YourServer" : "YourDatabase.nsf"; "YourForm")
To the users. When they click the button, a new document with your form is created. Then you use #Command([FileSave]) in an action to save the document. Usually one checks, using #dblookup, if there is already an entry fo that user an prohibits more than one document per user.
Then you create views to show the documents and see instantly:
How many users took part so far,
How many users selected option 1, option 2, etc.
You have all the information in one place, it is structured and can be easily read / found / evaluated.
Sending mails around would meen, that you have to collect that information yourself and count manually...
Which is a better User Experience / Design decision for opening a table row (in a business website)? To place an "Open" button like this:
Or, to allow the row to be opened by clicking anywhere on it?
Your question assumes that people understand that there is more information to be gained by "expanding" these rows in this table. As this is designed right now, there are zero hints for a user that they are capable of viewing more information inside the same view that they are using.
Option 1: Open button
Let's assume (dangerously) that people are knowledgable that they can use this table to view more info about a line item in this table. The button itself is separated from the content it is referring to, breaking Fitt's Law. Also, the label is "open", which most users would interpret as taking them to another page, or opening a new context. "View More" or "Expand" would be a better label.
Option 2: Click anywhere
This is slightly better than the button, as it clearly relates the action to the content. However, it still doesn't solve the problem of exposing the functionality to the user.
I would recommend a combination of both of these approaches, making sure you are solving for Fitt's Law as well as exposing a label that will tell the users what functionality is present in these table rows, and how to access them.
I have a simple question.
I have a lot of menuitems and buttons in my application. I try to remember to add ... in the caption to indicate that a modal dialog is followed.
But should I also add those dots for a non modal dialog. I try to search in Google but cannot find any clear answer. I use Win32 and Delphi.
Regards
The ... implies that some further input is required to complete the action of the menu item.
So, "Save" means that the menu item will cause the document to save, whereas "Save..." implies that the user will need to enter the name, or choose a file format or something before the file will be saved.
Typically the further input is entered in a popup modal dialog, but (a) not every modal dialog is a prompt for further information, and (b) hypothetically some other input mechanism could be used.
The '...' implies that the user will be given the opportunity to back-out of the operation.
This was in a user interface guideline book I read back in 1995, I can't seem to find a definitive confirmation online anymore.
I'd say that this depends strongly on your personal taste. I add ... whenever any new window is opened, be it modal or non-modal, to indicate to the user that he has to expect some other window to appear.
My guess is that there should be some Microsoft UI Guidelines document about that, but neither have I ever looked for something like that nor do I know of one.