Skip to content

Windward Core

Some of our most innovative features originate with the users of our software. Please use this forum to submit ideas for new features and enhancements to existing features. The more votes from users from different Customers an idea receives, the more likely the feature will be added in the near future.


  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

7 results found

  1. Font Awesome

    Hi Windward team!

    Windward does fully not support printing of Front Awesome: it does support it when running from the Designer and selecting the output = Word, but it does not support it when using html or pdf output. Your support team indicated that "the script and <i> class html elements required by Font Awesome are not supported currently by Windward html".
    The proposed workaround is get the images in a browser or copied elsewhere, screenshot them, and then bring in those images in an Import or Out tag.

    However, handling of images is very fiddly in Windward as it…

    32 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  RESTful Engine  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Would like the RESTful engine to be able to return plain text instead of base64 encoded response for CSV output

    Would like the RESTful engine to be able to return plain text instead of base64 encoded response for CSV output requests. Currently, all responses are returned base64 encoded which wouldn't be necessary for a CSV report just plain text would be better.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  RESTful Engine  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hello Reporter,

    This idea has been reviewed internally but has been declined due to lack of votes. Thank you for your idea, and please submit any other suggestions you have to improve the product!

    Adam Austin
    Product Manager

  3. Merge the printed documents

    We have letters printed based on the letter (unique)id so when there are 100 letters for example we do have 100 letters(documents) printed which is great and that is how we anticipate the outcome, along with that we have a mail merge process that merges all 100 individual letters to one document, this way the team which prints the letter will have to send the one file to the machine for printing all 100 letters instead sending 100 different individual letters. I want to check and see if we have any process that merges individual printed letters to one single…

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    declined  ·  2 comments  ·  RESTful Engine  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. RESTful engine async does not check for the validity of the report request and immediately returns a Guid. It would be prefered that the RES

    RESTful engine async does not check for the validity of the report request and immediately returns a Guid. It would be preferred that
    the RESTful engine checks immediately and return an error message instead.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  RESTful Engine  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hello Reporter,

    We have reviewed this request internally but have declined it for development. The reason is that the functionality you describe appears to contradict the asynchronous request type: to wait for errors before sending the response would make the request, in a sense, synchronous. We would recommend instead to check the validity of the request in your code that calls the RESTful engine to keep your asynchronous request, but also get this feedback. Thank you for your suggestion, and please submit any other ideas you have to improve the product!

    Adam Austin
    Product Manager

  5. RESTful Engine - Embedded Datasource in Request

    Currently when passing and XML or JSON data source within a REST request it has to be encoded into base64. It would be very valuable to be able to pass the XML or JSON data directly within the REST request.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  RESTful Engine  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hello Reporter,

    We have reviewed this request internally, but it has been declined due to lack of votes. Thank you for your suggestion, and please submit any other ideas you have to improve our product!

    Adam Austin
    Product Manager

  6. List Javelin in categories

    Why Javelin is not in the category list of ideas submission

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  RESTful Engine  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. RESTful Engine Error Response

    While processing through a dataset I use the following code:
    if(report.GetStatus() == Report.Status.Error)

    What needs to be added is a way to see and report back to the user what failed. Why is the report in an error state.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  RESTful Engine  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    I wanted to follow up on this suggestion. We have made many improvements to the RESTful Engine in recent years, so I wanted to ask if this was still an issue for you. We are looking to improve our errors in the future to be more clear, so if this is still an issue we will consider adding it to that effort.

    Thank you for your suggestion. I am setting this ticket to declined while we wait for a response.
    Adam Austin
    Product Manager

  • Don't see your idea?

Feedback and Knowledge Base