Invoking Task UI in Siebel 8 - siebel

I'm trying to invoke a Task UI in Siebel 8 and don't get anywhere.
I've added a button to an applet, with Method Invoked "LaunchTask" and
the following Control User Prop:
Name: Task Name
Value:
That button doesn't even show up in the UI. When I change the Method
Invoked to something else the button is displayed.
Does anybody have an idea why the button is not shown?
I've activated and deployed the task, and am running this on the
dedicated client against my local database.
I also tried invoking the Task from an applet server script, as
described in the bookshelf. That crashes the Siebel client.
Any help will be appreciated.
Thanks,
Thomas

Hm, I found the problem.
My responsibility didn't have access to the Task.
Problem solved.

Syntax to invoke from Button, Method Invoked should be "TaskLaunch".
Please update the method invoked and try it.

Related

Dialogflow CX | How to let the bot initiate the conversation?

Dialogflow ES has an event called 'WELCOME' which makes it possible for the bot to initiate the conversation.
How can I do the same in Dialogflow CX?
There is no entry fulfillment option in the Start Page of Dialogflow CX.
Edit:
Delete the 'Default Welcome Intent' route.
I am unable to perform this. I get the following error.
In 'Default Welcome Intent' change the intent from 'WELCOME' to nothing.
I get the following error. I have set the condition to true. I have also set the page transition to 'onboarding' page.
Please let me know if more screenshots are required.
To accomplish what you're asking, the easiest way would be to:
Open the "Default Start Flow" and select its Start page.
Remove all routes and add a new one.
This new route takes a "custom condition" in the form of true (in the condition pane, click on customize expression and then just type true) and goes to a new page
called "Onboarding" (on the bottom of the route creation page, click on new page and name it Onboarding).
Go to the Onboarding page and add an entry fulfilment "Hello there, how are you doing today?"
in this way every time the default start flow is activated (window is opened) the bot will use that fulfilment.
EDIT:
ok, i tried creating a new agent and i think i solved the problem.
it seems as though we can't erase the default welcome intent, but it doesn't matter.
i created two pages: onboarding and first page. from start i added an always true route to the onboarding page, and i did the same with the onboarding and first page. As you can see from the testing console we only get the expected behaviour for the second transition, look at this:
start page:
onboarding page:
"first" page:
After looking for info on the documentation i think i understood this: from the testing console, google doesn't let you see the actual behaviour of the conversation. If you see the screenshots, when i say "hi" and go the the onboarding page, i get immediately brought to the next page by that "true" transition. Since the same exact sequence is on the start page, the same behaviour should apply there: you only can't see it in the console because "opening the window" in the console is not the same as opening the conversation "in real life".
So, what i suggest you to do is create a new integration or develop a testing environment for the bot, say a website with the messenger integration, a telephony integration or whatever else, and test this onboarding on there. Speaking from personal experience, try with the messenger one maybe: you get a link and you just embed the script in any webpage (works well and easy).
It should work, as in, as soon as you open the conversation, the bot should go the onboarding page and say "hello there!"
So, I'm not sure what your end use-case is, but DFCX (at it's core) isn't exactly designed to initiate an unsolicited message because it's really just a language model with a bunch of features built on top of it.
With that being said, if you want to create a pop-up window for your website chat-widget, you can actually configure this in the integration settings with your embed code. Here's an example:
//The DF Messenger element:
<df-messenger df-cx="true" chat-title="Agent Name" agent-id="<your agent ID>" language-code="en" expand="true"></df-messenger>
//The window load script :
<script src="https://www.gstatic.com/dialogflow-console/fast/messenger-cx/bootstrap.js?v=1"></script><script>
window.addEventListener('dfMessengerLoaded', function (event) {
const dfMessenger = document.querySelector('df-messenger');
const openText = ('<The Text You Want To Display On Page Load>');
dfMessenger.renderCustomText(openText);
});
</script>
Please note this will only work if you have the DF Messenger Integration enabled on your agent. See the docs for integrating DF Messenger here
1.Use the attribute intent inside the df-messenger tag in your UI/HTML page
2.Then create a Custom Event in Dialogflow CX (By clicking on Event handler '+' icon)
3.Check the 'use custom event' checkbox and provide event name and provide a text response in fulfillment section of this custom event.
4.Finally provide this custom event name as value to the attribute intent(mentioned in step 1)
please refer to this document for df-messenger HTML customizations https://cloud.google.com/dialogflow/cx/docs/concept/integration/dialogflow-messenger#html-customize
According to Dialogflow CX documentation, the WELCOME event (although not visible in the Start flow) is also available. As you can see in this link and the picture below.
To invoke this event, you have to use the detectIntent method of a Session client. You'll need to specify the event name in queryInput.event.event of the request used in detectIntent.
Hope this helps!

How to execute Javascript from button click on d365 F&O

I need to know if it's possible to execute Javascript from a button click on d365 F&O. If so, how to do that?
I'm needing to call a URL that is only available inside of our customer's local network - it's not available over the Internet. So, I'm thinking Javascript is my only option. Not sure if this is possible in d365. Any help would be great.
TIA!

Azure LogicApp runs webjob and send email

I want to create an Azure LogicApps that has to launch and verify the status of a webjob. This is because I want to take an action if the webjob finishes its activities with an error and, in this case, the LogicApps has to send an email with an alert and restart the webjob.
I have tried to find some documentation about it on LogicApps site and in the editor but I can't find any connectors.
Any ideas, documentation or samples? Thank you
I thought my way could meet your requirements.
You could use a HTTP trigger to get the latest_run property with GET method. The URI would look something like https://{webapp-name}.scm.azurewebsites.net/api/triggeredwebjobs/{webjob-name}/. Then click advanced options, choose Basic Authentication. You could get username and password from publish profile or go to Webjobs on the Kudu then click the Properties. The trigger would be like the pic shows.
Then add a compose action, use HTTP Body as Inputs. After this , you could judge the status property. The whole flow would be like the below pic.
Note:when you use condition to judge status, you need to switch Designer to Code view, then change the value. The value should be "#outputs('Compose')['latest_run']['status']". Or you could refer my code view page.
Hope this could help you , If you still have other questions, please let me know.

ember.js: catching url enter event

In ember.js I need to trigger a modal box create when I enter inside an URL, and to trigger its destruction when i leave it.
Do you know what events i can observe?
Will they be triggered in the controller or in the route?
And, finally, where can i find the documentation for this? I couldn't find any in ember.js site
I tried the enter and leave event, but they are triggered only once, and in the wrong moment
Thanks in advance
Look at activate and deactivate hooks on the Ember.Route.
http://emberjs.com/api/classes/Ember.Route.html

Windows Phone app crashes when navigating back from a task

Some pages in my app allow users to click a hyperlink to launch the external browser via a WebBrowserHelper.
I'm carefully saving the app state in OnNavigatedFrom and restoring it in OnNavigatedTo, but when the user navigates back from the web browser into my app, the app hangs, then crashes.
I've carefully followed the great blog post on the Windows Team Blog, but can also reproduce the bug using the provided code there (just add a WebBrowserTask to one of the button click events on the DetailsPage; or in fact a send SMS task).
Can anyone else confirm this bug, or perhaps point out something special that needs to be done to overcome it?
Whoops! Yes it turns out in most cases you just need to resume the debugger to have the app come back to life.
However in my case there is also a bug in my own code. As usual.