Aware IM User Forums

I have used this before to capture web hooks. Once you have setup an Object for Sendgrid and the relevant Sendgrid event attributes and a User so the webhook can log in it works perfectly I assume you're referring to web hooks in general, not SendGrid specifically, because this will definitely NOT ...

Do you know if the functionality described above which you say should be in 8.1 would theoretically have the ability to receive Webhooks from SendGrid or Mandrill as described here: Hi Tom, I reviewed the Sendgrid and Mandrill docs. Most of this functionality is already supported by the AIM REST se...

I'd like to propose more convenient access to query string parameters, as well as POST, COOKIE and SESSION support. Presently, it's a pain to access the query string parameters. You have to create a persistent object, then create a process that takes that object as its input. Then you have to call t...

Actually, Vlad has informed me that this is on the roadmap for 8.1. I'm not sure if they intend to do the complete feature set I listed here, but at least some of this functionality should be implemented.

In the mean time, i'm sure you know you could create a BO to do that. I assume you mean creating an object to store manually-created log entries. Presently, I'm using the EXPORT action to create a log file, but neither of these approaches is ideal because the log entries are not correlated with the...

Even with Rule Evaluation level logging enabled, AIM's logging is very incomplete, making it difficult to debug rules and processes. It shows the result of each rule, but it doesn't provide any context for the result, such as the attribute values of the BO's involved. So if a rule fails, you often c...

Currently, the EXECUTE PROGRAM action is one-way. You can execute a program, but there's no way of capturing the output from STDOUT. I know you can do convoluted workarounds like having the program write the output to a file, then importing the file, but it shouldn't be this hard. We should be able ...

It would be convenient if AIM provided URL_ENCODE and URL_DECODE functions to make it easier to work with query string parameters that may contain illegal characters.

why not just turn the status bar off (which you can) and use the footer with the appropriate HTML to do the magic you need? It's easy to customize static elements in AIM, but not so simple to add custom dynamic elements. AIM does provide a JS API, but it's really only useful for interacting with ex...

Agreed. In its present form, the status bar is really only useful for the administrator. For instance, it makes no sense to display “Business Space” to end users. The real estate could be better used to display something like a message of the day and a notification center.

I had made such a request a few months ago on the forum and support said, it's planned for the next major release. Well, this post is from two years ago and there have been several major releases since then, but still no code editor. It would be nice to get an update from AIM support on when this w...

I think you're overcomplicating it. WordPress and AIM use completely different technologies, so there's no straightforward approach to integrate them. Given enough time and money, anything is possible, but if you're looking for a simple, step-by-step solution, you can use an iFrame to create the app...

As I mentioned to Vlad, my wishlist for REST consumption consists of the following items: Choice of using GET or POST If using POST, the ability to send a standard POST request or JSON. Ability to specify custom headers in the request. Receive the response in one of the following formats: Simple tex...

As we said many times before to our best knowledge there is no industry standard for consuming REST services, so implementing an out-of-the-box solution is very difficult. While there may or may not be an "industry standard" for consuming REST services, there's no question that 99% of RESTful API's...

Actually, it does save the value. The problem is that if the combo box has the "Value must be provided" option enabled, it fails the validation, even though the value was provided by the "CREATE WITH" action. I was able to work around this by setting an initial value in the attribute definition scre...