GSchinko

My feedback

  1. 27 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    TELL US MORE  ·  Joy Wang responded

    Please specify what kind of high availability is requested. For PI Integrator for BA to run in a highly available fashion?

    To support other applications that are highly available? If so, which ones?

    An error occurred while saving the comment
    GSchinko commented  · 

    Continued availability of reports in near real time is required. Some reports deal with factors related to safety, legal compliance, etc that are time-sensitive and need to be reliably published on schedule, regardless of availability of the single server that currently handles all integrator operations. Receiving such a report after a significant delay could have serious consequences, including inappropriate management decisions, lost productivity, or continuation of dangerous conditions beyond the normal response time.

    GSchinko supported this idea  · 
  2. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI Server » System Management  ·  Flag idea as inappropriate…  ·  Admin →
    GSchinko shared this idea  · 
  3. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PI Server » Notifications  ·  Flag idea as inappropriate…  ·  Admin →
    GSchinko supported this idea  · 
    An error occurred while saving the comment
    GSchinko commented  · 

    per KnowledgeArticle "String attribute are parsed to a number for REST web service", a similar problem exists with JSON property values that can be mis-interpreted as numbers.

    Please expand this request to include a "clean" method of dealing with this, perhaps by allowing the user to select a data type for the value being relayed to the JSON body.

  4. 8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PI Server » Notifications  ·  Flag idea as inappropriate…  ·  Admin →
    GSchinko supported this idea  · 
  5. 54 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PI Server » Notifications  ·  Flag idea as inappropriate…  ·  Admin →
    GSchinko supported this idea  · 
  6. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interfaces » PI Interface for RDBMS  ·  Flag idea as inappropriate…  ·  Admin →
    GSchinko shared this idea  · 
  7. 21 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PI Server » Event Frames (EF)  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    GSchinko commented  · 

    Would be nice to be able to specify a horizon of "how current must a notification be" for issuance

  8. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI Interfaces » Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
    GSchinko supported this idea  · 
    An error occurred while saving the comment
    GSchinko commented  · 

    This would be well met if the interface could support a UniInt Phase 2 failover mechanism. In a similar vein, this would also enable interface failover when the primary loses contact with its data archive, but the secondary is able to maintain its connection to a data archive.

  9. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interfaces » General  ·  Flag idea as inappropriate…  ·  Admin →
    GSchinko shared this idea  · 
  10. 17 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  PI Vision » Display Management / Displays Page  ·  Flag idea as inappropriate…  ·  Admin →
    GSchinko supported this idea  · 
    An error occurred while saving the comment
    GSchinko commented  · 

    These options would be of particular importance in an environment like ours, where development work is done on one Vision server, and the finalized results promoted to a separate, more heavily-protected Vision server, intended for "official" reports and displays that must be protected from accidental or unauthorized modification. Currently, attempting to modify an existing page in the "dev" server then promote it to the "prod" server results in duplicate displays with identical names.

    In the interim, a SQL script to re-name or re-number displays would be helpful.

Feedback and Knowledge Base

Posted ideas will have one of the following statuses.
Full definition of these statuses can be found on the Home Page.
No status
TELL US MORE
EVALUATING
PLANNED
IN DEVELOPMENT
COMPLETED
DECLINED